194 karma · joined September 21, 2018
Anyhow ¯\_(°ペ)_/¯ Rust is a great example of good engineering. There is a lot of old ideas put together in a way that makes the whole greater than the sum of its parts.
The only kind of strategy that seems capable of delivering on both scale and lifecycle is one where we enhance the environment to capture the CO2 for us and store it in the organic food chain simply by scaling it up to hold the extra mass.
Most likely we would have to enhance plains and deserts to become forests. Use regenerative agricultural practices and eat less meat. The big opportunity is in the oceans. There are wast “sea deserts” that could be transformed into more biological active habitats by using our industrial base to build some kind of structure to protect small life. Perhaps also disperse nutrients to accelerate biological processes.
That said, it is natural that any successful product goes through the explore, expand, exploit phases (see Kent Beck). And this is perhaps a sign that Rust is approaching the exploit phase, where changes should be slower and focus shifted to reducing overhead.
Perhaps a future Rust edition (next after 2018), will have a list of features removed as it's main selling point?
Still I agree with (out) boats. Rust should complete it's main concepts first. Then we can tidy our room. Promise?
I honestly don't want to bash JS, but typing is not it's strength.
(Not affiliated)
And I know nothing about browsers, GUI and front-end stuff, but Web-assembly is never the less very interesting for me, and I consider it the biggest thing since Docker.
Also is it even possible to standardize error handling best practices across entirely different software components like an OS kernel, a web service and a CLI tool?
OS kernel should not panic? Service absolutely should panic and restart to maintain availability and consistency if something unexpected happens (see Erlang) and a CLI tool has a human in the loop, sometimes.
“Under the radar” comes a new generation of better systems and components that learns from these learning vehicles of computing and will change how we deliver services fundamentally, but without k8s and Linux we would never have gotten there. Open source RISC-V co-evolved with seL4, WASI, webassembly and NATS comes to mind, but I’m sure the future will take its own path.
Logic is futile
I do however see one way masks would work. They act as a constant visual reminder to keep distance and not touching stuff. That works.