Well not entirely. You can use both on servers for delivering content, but shared hosting servers might not support more than PHP and maybe ASP.NET. The shared server provider probably publishes what systems are supported.
The whole point of GNOME is to do things “better” than those systems. If they manage to do so or not I’d say is subjective, but in my own opinion it provides me a better workflow. So yeah. People are indeed different.
Shame about the micro b port. Really don’t know why that is used still by anything.
Only if that perfect world with no Windows ever existing. Otherwise it makes perfect sense to exist, if nothing else than for archival purposes.
How is it proprietary-dependent?
how would you follow any of these?
People have tried and failed this concept for decades. It’s not a new idea, but it’s an incredibly large and complicated problem to solve, not only because package names and versions differ from distro to distro, or distro version to distro version, but the contents of the packages and what they support and are compiled with differ too.
In reality it’s not possible to get perfect, but with an absurd amount of effort a subset of support could be made. Your program just wouldn’t be able to have the same guaranteed feature set across distributions.
You can even setup your own build farm if you so desire, or if you’re using it in a research or commercial setting.
I agree with the premise, but unfortunately I’ve not yet had a system that worked well with Wayland, so I can’t make the switch yet.
That’s a bit narrow-minded. The issue is much more broad than “libs lol”.