Where did I say “Linux users”? Or for that matter, “only”? We were discussing the OP meme, not extrapolating beyond that to stereotype all Linux users. I mean… I use Linux, so why would I stereotype myself like that as well!?:-P
Also where did “complete inability to do so” come from? You can use emulation software such as Parallels or VMWare Fusion, or you could dual-boot into a 32-bit OS. So there’s 3 ways to accomplish the task. Granted, none as easy as if the Wine FOSS had decided to implement the task by itself, but just because they choose not to does not mean that any of those other 3 approaches will not work (bc they will).
Though yeah, I could see your last point. Tim Cook’s Apple making that business decision to switch from Intel x86 to the M-series chips and then not provide a Rosetta internal emulation system definitely can earn that for-profit corporation some negative thoughts, in comparison to FOSS. Then again, it sorta makes sense to me bc it’s a very niche case, to emulate old 32-bit x86 Windows programs on a 64-bit M-series modern Mac. They decided that the cost wasn’t worth it to them, when Parallels and VMWare Fusion already can handle the situation. So following that logic, shouldn’t we similarly be making fun of Wine, for also not stepping up to fill this gap? And all the more so bc it’s not a greedy for-profit megamaniacal corporation, but supposed to be there to provide for people’s needs, free of cost? I wonder what the logic behind that was? Perhaps that Steam exists now, so the need for such is again… just like for the Apple corporatization… too niche to bother with? If both for-profit Apple and FOSS Wine are in agreement here on that point, then I don’t really see the meme as much of a humorous joke. But maybe I’m just too unfunny to get it:-D.
What does Wine have to do with anything…? Wine is an implementation of Windows ABI and APIs, it has nothing to do with Linux’s ability to run 32 bit executables on 64 bit machines. AMD64 CPUs can run x86 instructions. 32 bit executables run natively on Linux, no emulation or VM required. Old (pre arm) versions of MacBooks have hardware that can run 32 bit instructions, but the OS simply doesn’t let you run 32 bit executables anymore without jumping through hoops.
A lot of your comment here makes no sense, tbh it reads like you’ve reached the limit of your understanding. And no we shouldn’t be “making fun of” the Wine team getting paid basically nothing for making an amazing product. Wtf?
@qqq@OpenStars before wow64 introduction, wine required 32 bit process and multilib to run 32 bit code, requiring 32 bit opengl/bulkan implementations
But it is possible to run 32 bit code in 64 bit process.
Wine in wow64 mode enforces 64 bit process to use only lower 32 bits address space and thunks 64 bit libraries via wine nt syscall interface to loaded 32 bit PE binaries. No multilib or even 32 bit process support required, 32 bit instructions executed as is. Also this allows using machine code translation layers (like fexemu) exposing native calls with same syscall interface.
wow64 maybe still limitted because it does not allow calling native libraries directly and increases overhead. win32 TLS code is using same fs segment register as linux 64bit TLS and workarounds may have bigger overhead, than using multilib
Where did I say “Linux users”? Or for that matter, “only”? We were discussing the OP meme, not extrapolating beyond that to stereotype all Linux users. I mean… I use Linux, so why would I stereotype myself like that as well!?:-P
Also where did “complete inability to do so” come from? You can use emulation software such as Parallels or VMWare Fusion, or you could dual-boot into a 32-bit OS. So there’s 3 ways to accomplish the task. Granted, none as easy as if the Wine FOSS had decided to implement the task by itself, but just because they choose not to does not mean that any of those other 3 approaches will not work (bc they will).
Though yeah, I could see your last point. Tim Cook’s Apple making that business decision to switch from Intel x86 to the M-series chips and then not provide a Rosetta internal emulation system definitely can earn that for-profit corporation some negative thoughts, in comparison to FOSS. Then again, it sorta makes sense to me bc it’s a very niche case, to emulate old 32-bit x86 Windows programs on a 64-bit M-series modern Mac. They decided that the cost wasn’t worth it to them, when Parallels and VMWare Fusion already can handle the situation. So following that logic, shouldn’t we similarly be making fun of Wine, for also not stepping up to fill this gap? And all the more so bc it’s not a greedy for-profit megamaniacal corporation, but supposed to be there to provide for people’s needs, free of cost? I wonder what the logic behind that was? Perhaps that Steam exists now, so the need for such is again… just like for the Apple corporatization… too niche to bother with? If both for-profit Apple and FOSS Wine are in agreement here on that point, then I don’t really see the meme as much of a humorous joke. But maybe I’m just too unfunny to get it:-D.
What does Wine have to do with anything…? Wine is an implementation of Windows ABI and APIs, it has nothing to do with Linux’s ability to run 32 bit executables on 64 bit machines. AMD64 CPUs can run x86 instructions. 32 bit executables run natively on Linux, no emulation or VM required. Old (pre arm) versions of MacBooks have hardware that can run 32 bit instructions, but the OS simply doesn’t let you run 32 bit executables anymore without jumping through hoops.
A lot of your comment here makes no sense, tbh it reads like you’ve reached the limit of your understanding. And no we shouldn’t be “making fun of” the Wine team getting paid basically nothing for making an amazing product. Wtf?
@qqq @OpenStars before wow64 introduction, wine required 32 bit process and multilib to run 32 bit code, requiring 32 bit opengl/bulkan implementations
But it is possible to run 32 bit code in 64 bit process.
Wine in wow64 mode enforces 64 bit process to use only lower 32 bits address space and thunks 64 bit libraries via wine nt syscall interface to loaded 32 bit PE binaries. No multilib or even 32 bit process support required, 32 bit instructions executed as is. Also this allows using machine code translation layers (like fexemu) exposing native calls with same syscall interface.
wow64 maybe still limitted because it does not allow calling native libraries directly and increases overhead. win32 TLS code is using same fs segment register as linux 64bit TLS and workarounds may have bigger overhead, than using multilib