The difference between Win32 and Linux is that the latter didn't realize an operating system is more than a kernel and a number of libraries and systems glued together, but is, indeed, a stable ABI (even for kernel modules -- so old drivers will be usable forever), a default, unique and stable API for user interface, audio, ..., and so forth. Linux failed completely not technologically, but to understand what an OS i…
Loss32: Let's Build a Win32/Linux
51–60 of 493 posts
Re: Loss32: Let's Build a Win32/Linux
#52But would you want to run these Win32 software on Linux for daily use? I don't.
Re: Loss32: Let's Build a Win32/Linux
#53Building GUI utilities based on VB6 instead of status quo web technologies might actually be more stable and productive.
Honestly, it’s probably faster and less resource intensive through emulation than your average Electron app :-/
Re: Loss32: Let's Build a Win32/Linux
#54'unfortunate rough edges that people only tolerate because they use WINE as a last resort'
Whether those rough edges will ever be ironed out is a matter I'll leave to other people. But I love that someone is attempting this just because of the tenacity it shows. This reminds me of projects like asahi and cosmopolitan c.
Now if we're to do something to actually solve for Gnu/Linux Desktops not having a stable ABI I think one solution would be to make a compatibility layer like Wine's but using Ubuntu's ABIs. Then as long as the app runs on supported Ubuntu releases it will run on a system with this layer. I just hope it wouldn't be a buggy mess like flatpak is.
Re: Loss32: Let's Build a Win32/Linux
#55The difference between Win32 and Linux is that the latter didn't realize an operating system is more than a kernel and a number of libraries and systems glued together, but is, indeed, a stable ABI (even for kernel modules -- so old drivers will be usable forever), a default, unique and stable API for user interface, audio, ..., and so forth. Linux failed completely not technologically, but to understand what an OS i…
Linux didn't aim to be an OS in the consumer sense (it is entirely an OS in an academic sense - in scientific literature OS == kernel, nothing else).The "consumer" OS is GNU/Linux or Android/Linux.
Re: Loss32: Let's Build a Win32/Linux
#56Crazy how, thanks to Wine/Proton, Linux is now more compatible with old Windows games than Windows itself. There are a lot of games from the 90s and even the 00s that require jumping through a lot of hoops to run on Windows, but through Steam they're click-to-play on Linux.
What are some examples?
Re: Loss32: Let's Build a Win32/Linux
#57It's my strong opinion that Windows 2000 Server, SP4 was the best desktop OS ever.
Re: Loss32: Let's Build a Win32/Linux
#58Damn, they didn't miss a spot to add a Loss comic reference. https://en.wikipedia.org/wiki/Loss_(Ctrl%2BAlt%2BDel)
Re: Loss32: Let's Build a Win32/Linux
#59Starting with FreeBSD might be easier than starting with Debian then removing all the GNUisms. But perhaps not as much Type II fun.
Re: Loss32: Let's Build a Win32/Linux
#60Building GUI utilities based on VB6 instead of status quo web technologies might actually be more stable and productive.