You must log in or register to comment.
Linux: I can’t stop you.
It could. It just doesn’t want to. Why would it? Its your computer.
If you want to delete / including the EFI partition turning your machine into a paperweight you should be allowed to do so.
It’s a good thing that new and unexperienced users who want to learn 😃 on the internet get recommendations such as “use
rm -fr /to remove the french language pack and fix your localization issues” and then ending up with an expensive, broken hardware (/s)I don’t want my mom to be able to turn her computer into a paperweight…
Don’t give her sudo permission then.
How she will install anything then
you can add
sudopermissions for individual users for certain commands only; and i recommend you would do that; i.e. give hersudopermission for installing/uninstalling applications, but nothing else.uninstalls the kernel package
Linux: i can’t stop dumb users (me) completely destroying everything with a bad console command
A great learning experience to not copy paste commands yoj don’t understand.
wget url | bash
Nice, now your computer is mining crypto for someone else or part of a botnet.
I’ll say it once, I’ll say it forever: Windows has better backward compatibility, period. Even compared to linux. Rebuilding an old open source linux app to work on a modern distro can be done, but it’s a process that could take hours or days. And if you don’t have the source code you’re shit out of luck. Have fun getting that binary built against a 1 year old version of glibc to work. This, incidentally is what things like flatpak, docker and ubuntu’s nonsense competitor to both (of which our hatred is entirely rational no really stop laughing) are trying to solve.
Meanwhile microsoft office still handles leap years wrong because it might break backwards compatibility with old documents. Binaries built for windows xp will usually just work on windows 11. Packages built for ubuntu 22.0 often won’t run on ubuntu 23.0. You never notice this because linux are a culture of recompilers. Rebuilding every last package once a month is just how some distros roll. But that’s not backwards compatibility, that’s ongoing maintenance.
Backwards compatibility, but at what cost?
I find it hilarious that the first architecture change in 10 years, that happened seven years ago, still causes anxiety and pain for people who don’t even use that operating system and probably never did.
I wonder how much Linux usership is owed to people being completely incapable of dealing with a minor inconvenience they once encountered (or only saw a meme about) on an apple product.
The sun puts out less energy than is wasted by people hating on Apple for completely and utterly irrational reasons.
Based on some of their arguments it feels like they’ve never actually used a Mac. “It’s for babies and old people” they cry, like there’s not an entire Unix system under the hood.
That’s like saying there is an entire Linux system under Android. Sure there is, but there is enough in the way to
make the kernel not really accessiblenot have access to many normal Linux functions (like ifconfig).Are Linux users really working in the kernel all that much? I’ve been doing support for Linux sysadmins for a decade and not once have I needed to touch the kernel.
I mis-phrased that, sorry. In the Android case, you can’t access a lot of networking functionality and other lower level access functions.
Running ifconfig responses with:
Warning: cannot open /proc/net/dev (Permission denied). Limited output.
Even though it is based on Linux, and has access to the ifconfig app, it’s not really something you can do. There are other things to consider like that. While you could try to give yourself root access, it’s messy and not something that’s really easy or encouraged.
In macOS’s case, it’s Unix to a point, but try installing NVIDIA cards in them (for CUDA cores). There are Unix drivers for Nvidia cards, for x86 and ARM, but even thought it’s Unix, it still won’t work.
How about running native Vulcan? It’s a major API for 3D graphics. It has a Unix driver, but still can’t work on macOS. Best that can be done is workarounds, but that’s not native and has issues.
There is Unix support for these, but macOS isn’t really Unix underneath.
