You gotta work on your Linux kungfu. chroot has always been around. You can install any distro, any version side by side. Now there is even DistroBox. Also, Apples switch from 680x0 to PowerPC to Intel, (Arm the exception), every time, Apple customers were told to pound sand. Imagine you spent 10 to 20 thousand dollars on hardware and equipment and software, shit adds up (it’s not just buying a Macbook Pro for these artists), just to buy it all again. That’s why Apple has always been called out for this. Windows forced updates are hilarious and have only gotten worse and worse over the years from what I hear. Linux can be updated live with no reboot. All my servers are setup like that and my work dev machine. Even the kernel gets updated live. Obviously Android and their forced data collection apps would be a huge no no for a Linux distro.
I’d say these aren’t just “problems” with the OSes. Problems are something you can fix yourself or find a workaround. You can’t work around Windows update, thousands and thousands of dollars of investment into the Apple eco system down the drain every time Apple switches architectures, or Google’s mandatory spyware apps.
Like, isn’t this a failure of the Wine approach (again: FOSS architecture) to keep up with hardware, more than an actual problem with using a Mac?
Dude, you think this is about 32bit libraries. It’s about way more than that. Apple customers paid money for OSX. Why would anybody think FOSS is responsible for fixing the problem Apple knowingly created and not just one time. Keep in mind, Microsoft solved this problem with their WoW64 translations layer (like WINE, but for 32bit Windows on 64bit Windows). Linux has a couple solutions, chroot or rebuilding and repackaging the binaries. Obviously there could be a 32bit to 64bit translation layer for Linux like Windows but why when you have chroot. Same thing can be done on other Unix-like OSes. Apple should have done this for each architecture change. There was no reason to f over their customers each time. Also, keep in mind, I’m not an Apple user, not ever. So it’s them you have to convince that they, “weren’t screwed over; over and over again”. Seriously this was a joke in the late 90’s. Now it’s just reached bullshit levels. Rosetta was the least Apple could do.
Especially when after digging in sufficiently deeply to understand it, you find that it’s actually a deficiency with Wine, not Apple.
WINE should fix this for Apple? WINE doesn’t fix it for Windows or Linux or any of the BSD’s or any other Unix or Unix-like operating systems out there. None of them. If Apple wants to use WINE as the solution, then maybe Apple should pony up some of the money they made on OSX sales and pay some WINE developers and make WINE a first class citizen in OSX. Valve needs WINE for their OS, they came out of pocket; engineers and money. Apple can do the same. Especially for how much their customers pay. There is no justification for dumping this on FOSS to fix Apple’s mess.
You gotta work on your Linux kungfu. chroot has always been around. You can install any distro, any version side by side. Now there is even DistroBox. Also, Apples switch from 680x0 to PowerPC to Intel, (Arm the exception), every time, Apple customers were told to pound sand. Imagine you spent 10 to 20 thousand dollars on hardware and equipment and software, shit adds up (it’s not just buying a Macbook Pro for these artists), just to buy it all again. That’s why Apple has always been called out for this. Windows forced updates are hilarious and have only gotten worse and worse over the years from what I hear. Linux can be updated live with no reboot. All my servers are setup like that and my work dev machine. Even the kernel gets updated live. Obviously Android and their forced data collection apps would be a huge no no for a Linux distro.
I’d say these aren’t just “problems” with the OSes. Problems are something you can fix yourself or find a workaround. You can’t work around Windows update, thousands and thousands of dollars of investment into the Apple eco system down the drain every time Apple switches architectures, or Google’s mandatory spyware apps.
Dude, you think this is about 32bit libraries. It’s about way more than that. Apple customers paid money for OSX. Why would anybody think FOSS is responsible for fixing the problem Apple knowingly created and not just one time. Keep in mind, Microsoft solved this problem with their WoW64 translations layer (like WINE, but for 32bit Windows on 64bit Windows). Linux has a couple solutions, chroot or rebuilding and repackaging the binaries. Obviously there could be a 32bit to 64bit translation layer for Linux like Windows but why when you have chroot. Same thing can be done on other Unix-like OSes. Apple should have done this for each architecture change. There was no reason to f over their customers each time. Also, keep in mind, I’m not an Apple user, not ever. So it’s them you have to convince that they, “weren’t screwed over; over and over again”. Seriously this was a joke in the late 90’s. Now it’s just reached bullshit levels. Rosetta was the least Apple could do.
WINE should fix this for Apple? WINE doesn’t fix it for Windows or Linux or any of the BSD’s or any other Unix or Unix-like operating systems out there. None of them. If Apple wants to use WINE as the solution, then maybe Apple should pony up some of the money they made on OSX sales and pay some WINE developers and make WINE a first class citizen in OSX. Valve needs WINE for their OS, they came out of pocket; engineers and money. Apple can do the same. Especially for how much their customers pay. There is no justification for dumping this on FOSS to fix Apple’s mess.
That does sound nice.