2 ms·

Why don't the developer do the shim themselves? You can always have a core and shell out the UI to the platform being used. One example is Celluloid [0] (GTK) a

Why don't the developer do the shim themselves? You can always have a core and shell out the UI to the platform being used. One example is Celluloid [0] (GTK) and IINA [1], both use mpv as their backend. Why not have something like libslack, libspotify (a real one), or libdiscord, then have a more appropriate frontend to meet the users where they are. [0]: https://celluloid-player.github.io/ https://celluloid-player.github.io/ [1]: https://iina.io/ https://iina.io/

flohofwoe 1y ago
...more code in the client that should really be part of the 'operating system', and if I need to do it myself anyway, why should I care about consistency with other applications? Such an idea only works if it is less work for application developers, not more. And I think the right place for that is the operating system layer, not the application layer.
- skydhash 1y ago
  Yes, but Linux is only the kernel, everything else is someone else project. A distribution is nothing else than a curated list of software projects. macOS is a good example of what you're proposing. The developer toolkit have a lot of nice frameworks (libraries) to help build apps. But that ties you to Apple. You can't expect consistencies across OS unless someone does the work to provide an intermediate layer, and then you loose on each OS nicest capabilities. It may not make business sense, but the most elegant solution is to have a core that is your feature set, and then flesh out each dependency according to the platform.