Every single one of them has to fix the same set of bugs in different ways even if they share a wm library like wlroots. So unless you manage to get a critical mass on your wm, there is no way you can maintain it on your own. If I believed in conspiracy theories, I would have said that Redhat designed it to make sure they can control the ecosystem, but I think it's just over designed in all the wrong ways.
I find doing more focused searches with bang patterns work well for me, I.E searching wikipedia, manpages, mdn etc directly. Sometimes coupled with LLM to more quickly understand the syntax because docs tend to be sparse with examples.
I still miss something for quickly finding random facts like "how long to boil an egg" but for programming the above works quite well.
I agree, but it also feels like it would be so difficult. It requires a ton of training, the UIs are not flashy so people are going to feel repulsed (I unironically found looks to be a big blocker when adopting open source tech) and finally Microsoft is going to lobby incredibly hard against it. I wouldn't put it past Microsoft to actively sabotage any adoption.
This excuse is as old as the hills and I've been hearing it since the late 90s, but historically there has been exactly zero training between versions of Office or Windows that changed a lot of the interface overnight. Office workers just kept using them like the rest of the planet.
Not to mention companies who moved on to Google Docs or the web version of Office. Or companies who moved to MacOS 15-10 years ago.
In my state back home the entire workforce moved to LibreOffice and, according to my sister (a government worker), everyone is doing fine. Recently I saw a German government worker using Office to produce a document and she mentioned that she "barely knows how to use it" and "just knows how to load templates, fill and print".
This hypothetical problem of "needs training" only seems to exist when you mention the words "open source".
> - It requires a ton of training, the UIs are not flashy so people are going to feel repulsed (I unironically found looks to be a big blocker when adopting open source tech), and finally Microsoft is going to lobby incredibly hard against it.
I think everyone agrees the costs are high, especially beyond monetary ones, but this stance on avoiding these costs is slowly pushing everyone into finding out how expensive is not having sovereignty.
Through its tech industry the US has over time acquired too much power over critical digital infrastructure that has already compromised governments. We know of Presidents/PMs/Legislators spied upon through their phones and computers, and also Microsoft itself involved in revoking email access to the ICC's chief prosecutor as retaliation/defense against investigations.
Sovereignty is too important for government, and since everyone needs to do it and get security right going for open-source with funded development and constant auditing is in my mind the only way.
The employees don't care about software sovereignty. They just want to do their jobs and get their paychecks. Fail to win them over and the transition will fail as well.
For me its how easy it is to extend. Kakoune makes it so easy to integrate with the rest of my system. I can often create any kind of integration I need with just 1-10 lines of code. In vscode I need to just hope that someone else built the integration I need as a plugin, because writing plugins is really painful.
I noticed it's far far more work to build a wm for Wayland than it is for Xorg.