> The rust-analyzer project was started at the very end of 2017 (first commit). At that time, the existing LSP implementation, RLS, had been providing IDE support for Rust for several years.
By 2017, Rust had just basic IDE support with RLS and it was already quite popular. I completely reject your theory that the success of rust-analyzer is due to "the fact these IDEs worked great". It was Rust's success, even while having quite poor tooling, that brought people in to work on improving the tooling (to a point most other languages never reach).
> it took surprisingly little effort to get to a prototype which was already useful as an IDE, which happened in Autumn 2018
So, yeah it takes little effort to get a basic IDE... that's where most languages (e.g. D, Nim) stop... the hard part is to get something that's really good.
> At that critical point, the company Ferrous Systems (which was newborn itself) stepped in to fund further development of the prototype.
So, rust-analyzer was not just a hobby project since at least 2018, when it got sponsored by a business.
> By 2020, we realized that what we had built was no longer a prototype, but an already tremendously useful tool for day-to-day Rust programming.
It took 2 years of work while sponsored by a real business to get to the point where rust-analyzer was considered "tremendously useful".
That's a "huge effort" on my book, not Google-level (and I never said that), but huge nevertheless. And to get to the same level as you get with Java in IntelliJ, for example, you can be sure it'll take about as much effort as was already put into it, maybe more.
[1] https://blog.rust-lang.org/2022/02/21/rust-analyzer-joins-ru...