That Rust is gaining both mind-share and market share.
A lot of the HN folks wage meaningless language wars that are a distraction from the actual success elements of Rust: namely that it removes a class of bugs by the mere virtue of your program compiling. Add to that a stellar quality and very dedicated community, sprinkle amazing tooling on top (semgrep filters, tree-sitter support, code-generation libraries) and it is a clear winner. Hence, "the writing on the wall" comment.
From HN and several other forums, plus a few companies I worked in, plus some meetups, I got the impression that the chief factor of slowing down Rust's adoption are a lot of C/C++ graybeards on influential positions that have an axe to grind against it and never bother to give actual technical arguments in a discussion. Unproductive and somewhat juvenile but hey, people being people.
That, plus the mind-boggling amount of C/C++ code that has to be rewritten should the world accept Rust as their successor is, shall we say, a very valid reason for its adoption to not be super fast. (And a fairly valid reason at that.) This problem sadly still exists. But with the Linux kernel starting to pay (some) attention to security problems, I have hope that such efforts will begin sooner rather than later.
A lot of the HN folks wage meaningless language wars that are a distraction from the actual success elements of Rust: namely that it removes a class of bugs by the mere virtue of your program compiling. Add to that a stellar quality and very dedicated community, sprinkle amazing tooling on top (semgrep filters, tree-sitter support, code-generation libraries) and it is a clear winner. Hence, "the writing on the wall" comment.
From HN and several other forums, plus a few companies I worked in, plus some meetups, I got the impression that the chief factor of slowing down Rust's adoption are a lot of C/C++ graybeards on influential positions that have an axe to grind against it and never bother to give actual technical arguments in a discussion. Unproductive and somewhat juvenile but hey, people being people.
That, plus the mind-boggling amount of C/C++ code that has to be rewritten should the world accept Rust as their successor is, shall we say, a very valid reason for its adoption to not be super fast. (And a fairly valid reason at that.) This problem sadly still exists. But with the Linux kernel starting to pay (some) attention to security problems, I have hope that such efforts will begin sooner rather than later.