Dynamic languages are good for prototyping, especially if a lot of libraries available
Dynamic languages are good for prototyping, especially if a lot of libraries available
Error: ‘o’ is not found in ‘S.O.L.I.D’
It’s easy to change display manager (except the case of keeping multiple of them to test out, if they are big and complex, like Gnome and KDE - there are conflicts). Some distros may have worse support for specific display managers, but I cannot say as my experience was relatively smooth for Debian, Manjaro, Arch, Endeavour and Artix. In Ubuntu I had some issues, but I could live with them for a time being because I couldn’t change the workplace OS.
But for init system it’s usually PITA. Many packages, including critical for system operation may have dependency on systemd, for example. In case of Artix Linux there are separate versions of packages for each init system that’s supported, if package has dependency on the init system.
Not only package manager - init system, wiki, display manager, community support, package freshness vs stability also play their role. There are many other points that are important too.
Also can be last cash grab before leaving with a golden parachute, as industry doesn’t feel healthy
Helix 🌚
I’m not sure the UI/UX is anyhow related to kernel development.
I3/Sway/Hyprland/other WMs are already much more superior to anything that can be achieved in Win/Mac desktops in terms of flow and performance. Only polishing is needed. Other desktop options like Gnome/KDE are fine and more lightweight desktops are okay too. They need polishing too, but already great.