We're also seeing symptoms of this in software support. Specifically with flatpak for example, as people start to recommend or wonder about flags (that have never existed) not working.
My last info was, that we don't process anything in parallel, as the old xml scrapers were not optimized for that. As we're moving to python scrapers now, we should be able to optimize the interface to handle more in parallel. That was the plan at least, but XML scrapers first need to be removed, as they hold back the API.
That more sounds like a you problem. No reason to play around with your setup, if you don't want to. Just hook it up to a NAS and play your files, has been working fine here for +7 years
Having worked with "the main dev" I can't say I share this view. It has been very nice to be able to pick his brain and hear his thoughts. It can be exhausting, when you want to improve things now, but come up with a better long term plan. I guess that's a language designer thing.
I don't think that's fair. If elm ever wants to replace js it only needs to rewrite the kernel modules, they govern. Otherwise the whole ecosystem would break in that case and yes, that would be a harmful feature.
Honestly, it's nothing alike. Refactoring in Elm is different, as the compiler will tell you if you did the correct thing when refactoring. The typescript compiler can only do a fraction of that, even if you type your stuff correctly.
Needing to type stuff in elm is mostly optional too. The compiler will still check it for you anyway.
Interesting, why are compilers special in your POV? Why do they need regular maintenance and why don't they allow extension via some kind interfaces, thus allowing for less maintenance?
> Unless the benevolent dictator pushes out a new Elm version that is not backward compatible.
That wouldn't break your build/deploy out of the blue, as you don't get force updated to the latest version.
And having worked on the 0.19 transition, it was in public preview for about 3/4 of a year and regularly discussed in the elm slack. When 0.19.1 came about, there were some more pre-release versions, where evan asked people to test and give feedback in slack. Can't speak for versions before that.
I've been doing a bit more elm (some at work) and I've tried to get into Reason from time. I always aborted on the first day. Last time I tried to learn ReactReason in december, I think their VSCode tooling wasn't working at all.
I'm pretty sure if your honest all you projects end up having this bus factor (check all your dependencies). If you really care to look, most projects are run by a small group of people.
Some even end up writing (abusive) issues about that https://github.com/flatpak/flatpak/issues/6006