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
Windows 11 has the anti-feature of not supporting the old processor anymore. Who knows why. Could be anything from simplifying QA and maintenance effort to not being able to (or not willing to) implement a feature on the older platform.
Compared to that, I don't know of a platform Fedora has recently deprecated. Linux usually takes a really long time to deprecate and remove support for old hardware.
criddell is wondering what thing in common Fedora and Win11 had that made switching to either of them preferable to just sticking with Win10, I believe. As in: why not just stay on Win10, unless it was lacking something that Win11 and—apparently, if it was a viable alternative—Fedora have? What was the thing they both had that Win10 did not?
Windows 10 is still supported until 2025 and nobody would be surprised if they extend it two more years. If I were setting up a new machine today, I would probably still install Windows 10. Anything new is an unknown from a security perspective.
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.
I didn’t mean locking features, especially native modules - didn’t write a single one, so personally I won’t miss it. I meant „some repos are more equal then other” mindset. It’s clearer in case of custom operators - they are considered confusing, unless you mean parsing and by parsing you mean elm/json or elm/url, then it’s cool.
By all means, I’m not saying those are crucial features or that they don’t have right to do whatever they want with their language. They can and they do. I just find this kind of atitude and reasoning patronizing.
Some even end up writing (abusive) issues about that https://github.com/flatpak/flatpak/issues/6006