I switched from macos to Linux because it can't stop babying users and being unnecessarily restrictive
I tried running a 2nd instance of Roblox simultaneously on macos 15 with another account but this shows up, if my mac can handle it then why can't it just let me do it? If I have two copies of an app like Roblox in separate User/Applications folders, macos moves them to the /Applications/ folder.
Sometimes it won't run apps claiming to be corrupted, so I then have to do sudo xattr -cr /Applications/someapp.app in the terminal and they run perfectly fine. It always nags me if I download apps from anywhere but mac app store. Some of these messages can only be gotten rid of by disabling system integrity protection, but then macos blocks you from running MAS apps due to having "permissive security".
I don't daily drive macOS anymore, I switched to Linux on my M1 mac where I can do whatever the hell I want.
My dislike for MacOS started with this. I had a WordPerfect document, and WordPerfect, but it wouldn't let me open it because it insisted that it wasn't a WordPerfect document. And despite the fact that I could open it in WordPerfect on other computers.
It's always been this "I know better than you, idiot" mentality that drove me away. I went back, briefly, when businesses started letting employees request MacBooks instead of Windows - given those two options, OSX is preferable. Plus, it was Darwin by then, and the important UI - the shell - was essentially POSIX.
I well always resent MacOS having the temerity to think it knew better than me, especially in cases when it was wrong but you just could not force it to do something.
I don't like Apple, but I like Macs. Obviously macos is better than Windows, but it's also Linux without the time spent figuring out why something isn't working.
I say that as someone who's had a go with Linux a lot over the years, but for a daily work machine I need the reliability.
They can piss off with their iClouds and iOS stuff though.
I think this is only conditionally true... A good AMD based system on say Fedora with a GPU that's at least a year old ... you really won't have much of a problem on Linux in my experience or much to fix.
it for sure was like a decade ago. i have a specific formative memory of using a series of sock puppets to game my way into being the 1,000th unique player on a game i liked a lot.
i think you could only do 2 simultaneously, and it might’ve been win7 exclusive lmao
I'm glad I'm not the only one who played Roblox growing up... But like over a decade ago. Weird to see it still around.
Random memories:
couldn't figure out how to drive vehicles (equip the drive tool and press T or something)
there used to be a FREE currency called TIX that they gutted
the old sound effects
the old forcefield effect
killing yourself precisely so that your head bounced onto the obby's next spawn point skipping the obstacle
-games were so much less commercialized, but they were also for the most part games made by other kids, they lacked the labor required to make a GAME game, but had charm. The fun games were FUN, and all they really offered in terms of monetization were VIP t shirts
desert Base Battle, ultimate paintball, ultimate build, sword fight on the heights, galleons, work at Pizza place, disaster survival
mashing yourself under geometry only slightly higher than you are, and then holding spacebar until you jump so hard your character model shoots out at a random tangent at Mach speed
calling my friend to play, using the wireless house phone, holding it against my ear with my shoulder for hours until I got cramps
constant status bars at the bottom from scripts included in free models "the maker of this place would like to thank xyzname for using their models!"
There are several different distro's built on asahi IIRC, asahi is more of a Mac platform for distro's than a distro itself if I understand the project correctly.
I have definitely looked into Asahi awhile ago, and knew that was the big one. It wouldn’t surprise me to learn that’s the only one, but didn’t know if maybe there were more.
While the app running permissions of macOS have become extremely obnoxious, you don’t need to disable system integrity protection. After macOS refuses to open an application, open system preferences -> security and there will be a button that says „open app anyway“, which you then confirm via password or fingerprint.
My memory is probably hazy (it's been a while since I used macOS) or it might've been removed but I recall that you were able to hold a key on the keyboard to bypass it as well. You'd have to right click the application, then hold down the key, and while holding it down click "Open".
I’ve never HAD to turn off system integrity for any reason, and I download all sorts of dodgy software from disreputable authors. It’s annoying as heck to micromanage permissions for non-MAS apps but I don’t think disabling integrity is worth it
We've been mucking around with how to pre-configure Raspberry Pis after flashing at $DAYJOB and basically, the way the Raspberry Pi Imager works is that it writes a firstrun.sh onto the SD card which gets run during first boot.
How does it know to not run that script from the second boot onwards? Well, one of the lines in that script is:
Oh yeah, we only want to pre-configure it with a static IP address on its Ethernet port, so that we can SSH into it in a controlled manner and then we intend to do the rest with a deployment tool.
Yeah, that is a very good question. It's one of the last commands in the script and initially I thought they had set up the script so that it would abort, if any of the commands before it would fail.
But then a colleague pointed out that it's actually the opposite. So, you can tell the shell to abort execution on error by running set -e. But what they had written at the top was set +e, which explicitly turns that off (even though it should be off by default).
The last command in the script is also exit 0, so it always indicates success.
So, yeah, they seem to have knowingly made it so that if the script fails, then it doesn't retry or anything. It tries to plough through as many of the commands as it can manage (ignoring any that fail on the way) and then it always deletes itself.
I guess, it's not as egregious of an assumption, because it only runs on a fresh OS. That's a pretty controlled environment to be executing in, so the chance of something going wrong is rather low.
Well, and the other question is what else would you do? If the script fails and you don't delete it, it's going to re-run on the next boot. What's going to be different on the next boot to make it succeed then? Might as well do as much as you can and then quit...