26 ms·
> the rest of the business is completely illiterate about anything even slightly technical It is that moment of realization that you're entirely responsible fo
by sshine 4y ago
> the rest of the business is completely illiterate about anything even slightly technical
It is that moment of realization that you're entirely responsible for the fate of the company, and you either think "I better tread carefully" or "This should be rewritten in Rust."
- weego 4y ago"We need a new build system that's built on streams"
- nickpeterson 4y agoRust may still be a bit too pragmatic, perhaps you could use a language you wrote yourself?
- the_sleaze9 4y ago"Aaaand that's the container address orchestrator -- it's written in Haskell by that one guy a few years ago."
- ilyt 4y ago"We wait for it to break for last 3 years just to have excuse to run k8s"
- mkl95 4y agoIt reminds me of some Python threading monstrosity a guy wrote at my first job. He said something like "this is my own take at async".
- ptx 4y agoTo be fair to that guy, the Python standard library provides a multitude of incompatible takes at async already, none of which covers all common use cases. The newest take (asyncio) doesn't integrate with external event loops, so unlike similar libraries in C# and Kotlin, it doesn't work with GUI libraries, not even the one in the standard library (tkinter). The third-party asyncio alternative Trio, on the other hand, has recently added "guest mode" [1] to plug in external event loops, so maybe that will become the one true way to do async. [1] https://trio.readthedocs.io/en/stable/reference-lowlevel.html#what-is-guest-mode https://trio.readthedocs.io/en/stable/reference-lowlevel.htm...
- sshine 4y agoYes, I've heard Rust has a high learning curve. By making things in your own language, you stay ahead of the learning curve while others stay perplexed.