Hacker News Reader

Comment by badsectoracula | Hacker News Reader

> The main difference is that most Windows apps are statically linked.

No, the main difference is that on Windows the GUI libraries (USER32.DLL, etc) are considered part of the OS and have an API that remains backwards compatible. The applications are not statically linking the GUI libraries, they are dynamically linked against them, pretty much like on Linux.

However on Linux the GUI libraries do not care a bit about preserving backwards compatibility (see Gtk1, Gtk2, Gtk3 and soon Gtk4, see Qt1, Qt2, Qt3, Qt4, Qt5 and soon Qt6 - although in Qt's case they cant do much thanks to C++'s ABI issues and TBH i wouldn't expect them do since Qt is primarily made by a company with interests in providing a crossplatform UI library, not the native GUI library for Linux).

Windows simply provides a much richer API than Linux as a standard that applications can rely on.

View on HN

There are *-compat[1] packages for backward compatibility. You are welcome to support them, if you really need them.

[1]: https://pkgs.org/download/-compat

Compat libraries are band-aid to the real problem that is the developers of the libraries not caring about backwards compatibility and the only fix is to cultivate a culture of caring about backwards compatibility instead of writing excuses. Compat libraries are only applicable to a few libraries (where are the Gtk1-compat libraries?) and all they do is freeze the API in time without any updates to the provided functionality (where are the SDL1-compat libraries that work seamlessly with alt-tab in desktop environments, like SDL2 does?).

> where are the Gtk1-compat libraries?

Here: https://github.com/openSUSE/gtk1-compat

> and all they do is freeze the API in time without any updates to the provided functionality

Yep.

> where are the SDL1-compat libraries that work seamlessly with alt-tab in desktop environments, like SDL2 does?

It's open source. If you need it, take care about it, OR pay to a somebody else to take care about it. Nobody will work for you for free.

It's like roads. Roads are free, because lot of drivers are using it every day, so they are paying taxes to build and maintain them, but road to your house in the middle of nowhere is not free, because nobody shares it with you. However, road making tech is open sourced, so you can build your own road if you need it.

Of course, you can use paid road, if you want, because they are providing better service for small pay per ride, or you can hire developer company to build private road to your house and then payback loan to a bank. It's up to you.

But statements like "free and open roads are bad, because road to my own house costs lot of money for me" is just childish play. Roads are not free to build and maintain. Roads are free and open to use, but only because they are paid by someone else. For your own private road, pay with your own labor or money.

Reply on news.ycombinator.com