Agreed. We've almost eradicated our usage of JS Date - fixing plenty of bugs along the way, and then I extracted thousands of lines of conversions and formatting from our production app (scheduling focused) into a temporal-fun package to make it Temporal more ergonomic for lots of common cases.
Word of warning Temporal relies on the Intl API for formatting, and support in Chrome is very limited due to their binary size constraints. As a result, you'll need to polyfill unsupported languages using format.js
Location: Seattle
Remote: yes, but not necessary
Willing to relocate: no
Technologies: DevOps, Kubernetes, Rust, Ruby, Typescript, Svelte, VueJS
Résumé/CV: https://anowell.com/portfolio
Email: anowell (at) gmail
Part-time only!
I'm bootstrapping a new business (a makerspace), but would love to complement it with a part-time role. 13 years of experience loving both IC and director type roles. Scaffolding/architecting new distributed system components, cloud operations, developer experience tooling, and mentoring have always been front and center for me, but I'm fairly versatile, even loving documentation and process development. Best fit is probably a role where I can help get something off the ground and mentor someone more junior to take ownership of it.
I'd take a pretty steep discount from my historical rates for the right part-time role and schedule flexibility.
This is roughly my story with the added note that I find that Github activity inversely correlates to how much Netflix I watch. I currently average about 3hrs /wk of TV time and probably about 15hrs/wk on personal projects.
I am excited to write some Rust in the browser, and have been tinkering with what it might look to have a rust frontend framework with ergonomics comparable to what you might expect in other high level languages. (https://anowell.github.io/quasar/)
That said, I agree that more people will want to work in higher level languages, though I kinda suspect "most" are going to still prefer Javascript for the forseeable future - so I sorta see JS compiling to WASM as inevitable.
It's funny... the tactic that ReactNative runs for JS in different environments may well be contrasted with a "BrowserNative" library that bridges browser UI with another compiled (webasm) language.
I've been wondering this myself, so thanks for the link. Looks like it lives under the label: "Proposals we might consider in the future".
I've been building a [super early/experimental] rust frontend framework (https://github.com/anowell/quasar), and going through Javascript to manipulate the DOM is the cause of plenty of frustrations and limitations, so I'll be keeping an eye on this.
fwiw, I find the long term support pretty minimal. I'm only slightly more conservative in my use of`pacman -Syu` than I would be with `apt-get dist-upgrade`. If I notice a kernel or DE upgrade, I might hold off until the weekend on the off-chance that it needs a bit of extra maintenance. I appreciate handling these changes in smaller batches, as opposed to the 6-month system-wide major upgrade cadence. Of course, if I was just jumping between LTS releases, maybe only dealing with serious maintenance every other year would be an appealing trade-off.
(of course, I don't mean to undermine the argument for hesitating to jump to Arch on the grounds of maintenance. It certainly takes thinking about maintenance more often.)
You might checkout the literal optimizations that ripgrep does. IIRC, the underlying regex lib is optimizing a few classes of "simple" regexes with SIMD to achieve better perf than the first handwritten code in that article.
In addition to the other responses, the ecosystems around Rust ML (e.g. scientific computing) are still very early and the Rust ML community itself is still fairly small. Take a peek at arewelearningyet.com
This is solid. I'm an engineer at Algorithmia, and this caught our attention as the sort of project we love to host as a service on our algorithm marketplace. We've already made note of it for our team to consider adding (thanks to the generous MIT license), but I wanted to reach out in case you'd rather add, own, and optionally monetize it on our platform yourself. Either way, this was a great read with impressive results.
It would seem that your desire for a divine book is one that centers on human advancement and academic knowledge. If God's highest desire was for our self-advancement, perhaps the bible might look more like what you described.
npmjs.com/package/temporal-fun