There's going to be an online Linux App Summit this November

Which usually end up on some obscure command line (so modern... )

Speaking as someone who generally avoids the command line, when it comes to troubleshooting I prefer it. It's a lot easier to follow instructions to do command line stuff than to do GUI stuff, and it tends to be a lot less subject to change between versions. And it's more powerful for that kind of thing. So to me, the Windows tendency for troubleshooting instructions to be based on doing some weird tucked away GUI thing is a weakness rather than a strength.

We'll have to agree to disagree on that one (I could develop more, but I feel like it's not the right place to do so)

There is no real fragmentation in the Windows ecosystem because you don't have a choice.

Tenchically the windows linker is significantly more fragile.
They solved muti-versioning by namespacing all the symbols.
Whilst that works, it significantly reduces the ability to just test to see if a different version of library X works better than the original one.

There is fragmentation in Windows 10 now, thanks to their build / update system.
You now have release.build. if you are running 2004.#### then you can run WSL2, if you have 1909.##49 versions higher than work allows me to run, then Microsoft has backported the WSL2 stuff...
Oh, and if you don't have a specific build or later, if you have certain virtualization features enabled, you can't run VMWare workstation...
While this is a very particular example, it does show that there can be incompatible issues within Windows 10, as they are basically now doing what MacOS X did for many years, just doing small changes, but big enough to cause issues.


Last edited by slaapliedje on 27 Aug 2020 at 1:33 am UTC

There is no real fragmentation in the Windows ecosystem because you don't have a choice.

Tenchically the windows linker is significantly more fragile.
They solved muti-versioning by namespacing all the symbols.
Whilst that works, it significantly reduces the ability to just test to see if a different version of library X works better than the original one.

There is fragmentation in Windows 10 now, thanks to their build / update system.
You now have release.build. if you are running 2004.#### then you can run WSL2, if you have 1909.##49 versions higher than work allows me to run, then Microsoft has backported the WSL2 stuff...
Oh, and if you don't have a specific build or later, if you have certain virtualization features enabled, you can't run VMWare workstation...
While this is a very particular example, it does show that there can be incompatible issues within Windows 10, as they are basically now doing what MacOS X did for many years, just doing small changes, but big enough to cause issues.

Host hardware can only run a single VM platform at a time. You can't run ESXI alongside KVM, HyperV, or any other virtualization hosts. Enabling low level virtualization on any host is mutually exclusive with other hosts. That's true regardless of the OS. So it makes sense if you enable HyperV you can't run KVM for example. It's been that way for a really long time. This isn't a Windows 10 thing or even a Microsoft thing. Virtual Hosts/OSs want full control of all the hardware. If you enable WSL2 you're running both Win10 along with the Linux distro in HyperV. That is why you can't run VMWare workstation or KVM/Virtualbox on Windows 10 with WSL 2 enabled.

Besides, that isn't even what my point originally was. My point on fragmentation had to do with developers trying to write distro agnostic programs (games) for Linux natively and being frustrated by our ecosystem. It didn't have anything to do with VM hosts being mutually exclusive.

By the way SuperGiant won't be making a Linux port of its upcoming game Hades. They heard community reports that it works good enough on Proton and they hope that works out well for us. I wonder if it's just our anemic marketshare. Or maybe it's stuff like the Steam Linux Runtime based on Ubuntu still using an ancient version of GCC that breaks on modern OSs. Regardless of the reason, the end result is we've lost another Linux friendly developer for the time being. I can't help but think we create our own special hell for ourselves by loudly clamoring for Linux support and then driving developers away with low sales and a frustrating development experience.


Last edited by randyl on 27 Aug 2020 at 9:32 am UTC

I can't help but think we create our own special hell for ourselves by loudly clamoring for Linux support and then driving developers away with low sales and a frustrating development experience.

"driving developers away with low sales" is a kind of weird turn of phrase. It's not like we Linux users create the low sales. Low market share is our biggest problem, for sure. If it was high, developers would, as they do with other platforms, gripe about its problems but work with them anyway.

I can't help but think we create our own special hell for ourselves by loudly clamoring for Linux support and then driving developers away with low sales and a frustrating development experience.

"driving developers away with low sales" is a kind of weird turn of phrase. It's not like we Linux users create the low sales. Low market share is our biggest problem, for sure. If it was high, developers would, as they do with other platforms, gripe about its problems but work with them anyway.

Good point. What I had in mind when I wrote that is the "no tux no bux" type of mantra that gets thrown around when developers don't meet Linux users demands. We withhold our money until we feel our laundry list of expectations are met. Maybe it's stretching a bit, but I feel we're a very hostile crowd when our expectations aren't delivered on a silver platter with a thank you note. I've seen studios comment in the past that they've delivered Linux ports, as the community of users demanded, but then never saw sales for that actually materialize. Maybe studio expectations are high. Maybe there is just a very vocal crowd that sounds disproportionately larger than it is and studios didn't do enough actual market research. Whatever the case, whenever we're told, no we're not getting a native port, Linux land seemingly becomes very hostile and institutes a hostile campaign of negative feedback and even harassment sometimes. I know I've been guilty of that in the past and I think it not only promotes a toxic discourse, it sets us back. I probably could have communicated that much better. Sometimes I get tired of hearing myself pontificate so I try and summarize without better explanation. :D

Anyway, I guess from my perspective there is a problem, but it doesn't appear to be broadly shared, especially here. That's okay. I support this site because I think it's doing great work to move our ecosystem forward, not because I agree or am agreed with. My hope in these discussion is to promote critical thinking and get people to ask questions or look at established paradigms from different angles and perspectives.

By the way, on my earlier statement of Windows 10 fragmentation. Flight Simulator 2020 apparently requires 2004.