Exactly this. It always surprises me when people get bent out of shape because there is an option that they don’t like. Even worse when someone makes a choice they don’t like. “Who the fuck cares. Let them do their thing. be grateful you have a choice.”
Don’t be so disingenuous. The same shit happens on Windows. And there is no guarantee that your drivers will work between Windows versions.
100% agree. The computer I have now, I only bought because I needed more cores and ram for my docker dev environment. But I had a Yoga 2 Pro. It worked great and was fast for most of what I needed. I gave the machine to my cousin so he could learn to program on it. Still a fast machine. Doesn’t play video games, but it didn’t play video games when I bought it either.
I’d wager that is true. I know, for sure, you can start one compositor inside another compositor. I do this all the time for gaming with gamescope.
Started on Slackware too. I remember building my own kernel and having to make sure it fit on a 1.44MB floppy.
make menuconfig
Nonsense. It has always been listed on the box if there is support. Same as all the other OSes. How many times have you bought random used Windows hardware to see if you could install MacOS on it? Nobody buys random Mac hardware to see if they can install Windows on it. There were Hackintosh’s but when some didn’t work out, nobody blamed MacOS. Back when Windows ran poorly on Intel Macs because of poor support, Nobody blamed Windows. It’s a double standard.
Shocker, you bought hardware with a compatible OS. That’s the dudes problem. He didn’t buy hardware compatible for Linux. 1984, so I know you are well aware, you have to buy hardware that is compatible with your OS.
Make Local LUGs Great Again.
No source to compile it yourself?
You have a OnePlus device? You can go to EDL mode to unbrick.
With WINE you wouldn’t need USB pass-through. Only if you are passing the hardware into a Virtual Machine. The pass-through just tells the Host system not handle the device. But you actually want the HOST system to handle the device. WINE is just translation, not virtualization. (or Emulation, haha)
P.S. USB pass-through does work really well in VM’s. If WINE doesn’t work for you. You could always keep around a Windows VM for the occasion you need the msm flash tool.
Msm flash tool
If that’s all you need. I bet you could just run it from WINE. I updated my PS5 controller using the PlayStation flash tool or whatever it’s called. I used Bottles to do all the WINE stuff. Just installed the flash tool and it worked like it was Windows. Pretty shocked if I’m being honest.
I’m convinced they all live in the moms’ basement eating chicken tendies.
Negative. Windows on Desktop uses vendor lock-in to maintain it’s user base. It’s been that way for nearly 30 years. People only think they are choosing Windows themselves. Anywhere Microsoft can not enforce vendor lock-in, Linux dominates. Even IoT, a brand new market (well it was brand new ten years ago), 80% dominated by Linux. Microsoft had to make Windows free for IoT and 9" or less devices just to try and be competitive. People only think everything is made for Windows, because OEMs are forced to sell a Windows license with every PC or lose their volume licensing deals. That means every OEM has to spend engineering dollars on Windows drivers, software, and testing. When your business has very thin margins, you can’t afford to have second or even third engineering efforts for competitor OSes. Imagine how Linux would be if PC companies were spending engineering dollars on Linux for the last 30 years. Right now the money comes primarily from server sales money. If there was demand for Linux on Desktop in the workplace, there would be tons of competing FOSS Group Policy implementations.
No point. Sleep works great and live updates are flawless.
CPU interrupts. There are timer interrupts that can be used for this. In hibernate, only a tiny fraction of the CPU is changing the transistor states. A transistor only uses power when it changes state; i.e. “off” or Hibernate. Transistor state changes when you cycle the clock on a CPU. Anyways, set the register for the timer interrupt and signal the CPU for Hibernate. The timer circuit is still listening to the clock while the rest of the CPU stops listening to the clock. Each clock cycle you subtract one from the register. When the register reaches zero, the timer interrupt wakes the rest of the CPU. Just like moving your mouse or pressing the power button; they signal an interrupt which wakes the CPU.
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.
When distro maintainers started building and shipping 64bit versions, they didn’t include 32bit libraries. You had to make a chroot for a 32bit distro, then symlink those libraries in among your 64bit libraries. Once distro maintainers were confident in the 64bit builds, they added 32bit libraries. In the case of Windows, Microsoft created a translation layer similar to WINE called WoW64 (Windows on Windows64). Apple is the only one who said, fuck you buy new software, to their customers. Rosetta is the first time Apple didn’t tell their customers to go pound sand; probably not by choice.
Would be fine. The problem is, Microsoft is encrypting drives and not telling anybody about it. Average users have no clue what any of this is and are completely unaware they need to create a passphrase for safe keeping.