To me -- this seems like an obvious candidate for a future 'billion dollar' mistake retrospective essay.
How and why is it that 'support fast compilation' isn't a necessary pre-condition for any modern language hoping to achieve serious usage?
With rust in particular -- it seems like a whole lot of the slow compilation behaviors are not fundamental to any of the most important aspects of the language ...
Is there anyone out there who has tried to fork the rust ecosystem in a way which deliberately breaks compatibility in order to chart the simplest path to a fast, scaleable compilation strategy for the language and ecosystem?
I have a feeling that such an effort -- rust with some misfeatures removed, and with the package system simplified in order to speed up compilation would actually take off and be able to replace the current ecosystem relatively quickly ...
MeetingsBrowser•5h ago
When choosing between languages, compile times should be a tie-breaker at most. If Rust had focused on super fast compilation from the start, it probably would have slowed developing the features that actually made it successful.
Its like a startup that spends forever building the perfect scalable backend instead of just solving customer problems. The hacky solution usually wins.
> Is there anyone out there who has tried to fork the rust ecosystem ... I have a feeling that such an effort ... would actually take off and be able to replace the current ecosystem relatively quickly
Forking the entire Rust ecosystem seems pretty unlikely to work, but everything's open source so anyone can give it a shot.