Do you feel threatened that Russia and Iran will succeed in conquering all of Europe and the Middle East? I see it more like a couple of misbehaving misfits. That's very different than say, WWII.
One could argue that human learning is not all that different from machines training on data. We are all regurgitation our own experiences and knowledge to some degree. We certainly have things that machines don't, but LLMs can definitely come up with novel things that were not in the training data.
Conversely, most of the high impact bugs are also written in C and C++, because they rely on "coding style and engineering practice" to be correct. Rust raises the floor on this by a lot.
Since the Rust support in the kernel is not optional, it already has an impact on platform support, no? Or maybe they are using the gnu toolchain to avoid that?
> Less skilled co-workers will make mistakes that will have more consequences when the language is more permissive.
Even the most skilled engineers are going to make these mistakes sometimes. That's the whole point of more restrictive tooling, and why Rust has exploded.
Don't get me wrong. I love Lisp, and use it in some personal projects. But I wouldn't want to use it in must not fail scenarios unless those situations can wait for a human to fix the running image.
The median alone doesn't paint the whole picture. We need to compare the spread as well. The median doesn't care if you make just under the median, or $1 a month.
I'm happy to see these improvements. One thing that has always been annoying with Emacs is how much configuration is required to get a modern editor going. Things like Doom Emacs, and Spacemacs try to solve that problem, but both feel far removed from vanilla emacs. I wish Emacs came with several presets so with a single line, you could transform the editor to different base points. For example, most devs want treesitter highlighting and LSP enabled by default. Why not have a preset like (preset-base-ide-1), so we don't need 200 lines of configuration before we can function? Instead we could build off of a much closer starting point.
I tried Helix for a few weeks and found it to be less efficient overall. Now granted it's hardly fair to compare 3 weeks to 20 years, so maybe with more time I might change my mind. I really missed vim's . key to repeat the last command for example. I think the learning curve for Helix is probably better than Vim, so if you haven't learned vim, it might be worth it. The other challenge though is the ubiquitous nature of vim and vim emulation.
I have felt this many times. However, the effort involved in writing code does not indicate the amount of issues that code may have. This is why I prefer Rust to C++ these days - it just removes 90% of the development tail, which can be quite long in C++.
It's funny how people take this perspective for Waymo, but when it comes to Tesla FSD, they are much less forgiving, even though I think Tesla's performance is at least as good, if not better.