Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "sudo rm google"
-
linux rant number 23094823094
Linux is a marvel of modern engineering. Well, at least in a sense that it somehow manages to work despite its design.
Basic commands like ls, grep, rm, cp (think busybox) do work predictably. Given that some of them are older than you and me combined (grep is 51 years old), it would've been weird if they didn't.
Yet, when comes the time to configure linux itself, there is no right way to do it — there are 5 or 6 wrong ones.
The wrong way number 1 to configure linux is to use predictable commands and their combinations. You know, cat + grep some config files, then awk to change them… If you do it, you will instantly break your system to the point that you'll have to back up your data, reinstall everything and put your data back.
All the other wrong ways are wrong because each of them will break your system in their own unique way. All of them kinda-sorta do what you want, at the expense of messing up some other things that have nothing to do with what you were trying to fix. The worst way to use them is combining one wrong way with some other one, like configuring xorg directly and then using ubuntu-specific userland config tools. This will instantly break your system too.
You'll have to google/chatgpt your way through historic quirks that are somehow still there in 2025. Remember: the worse the shell command looks, the more likely it is that it's the right way (or at least the least wrong way) to do things in linux.
Some minimal distros like alpine is a notable exception, in a way that they're more predictable, but they will become useless the moment you try to get some actual work done. I've used alpine as my desktop os for quite a while. I know what I'm talking about.
If you want so much as to install a browser, you'll have to use flatpak. But flatpak will only bail you out so many times. Your colleagues, and people that write tools that your colleagues use, are using macos, windows or ubuntu. You'll have to use whatever they're using, and if it uses glibc/is not in flatpak, well, tough cookies.
sudo apt install fuse breaks ubuntu instantly — it won't boot into graphical desktop anymore until you reinstall everything, including systemd, and do initramfs. Why does it do that in 2025? who knows.5 -
Went to a hackathon and tried to use ARCore. Most painful experience of my life. There are so many issues and critical bugs that I can't even fit them all into a 5000 character rant, Google has shittier code than a highschool startup.
So instead of typing 5000 characters I'll just save you all some time. If you're forced to use ARCore, don't even try to use the AcquireCameraImageBytes or related apis for actually accessing the camera feed. Just use unity's screen capture API (draw an invisible rectangle on the whole screen, make a texture, readPixel entire rectangle). Turning off all models for 1 frame and taking a screen capture is easier, faster, and somehow more optimal than using Google's code.
Also, they released Augmented Faces on Friday. Their demo plainly doesn't work the way they intended on many devices because the list never gets populated since their engineers are dumb fucks. Just force the face mesh to always remain active and you'll instantly support all devices! You can deactivate it using your own methods but Google's doesn't work on many devices. There's an issue in their repo about this that they are plainly ignoring.
Also if you're interested I have a (working?) engine to use Object Detection for interactions within AR + a create your own adventure game demo made w/ object detection + ar on my git:
https://github.com/pshah123/...
My code is 100% crap so definitely don't use it in production but I was able to get the individual pieces working so hopefully this helps someone! Unless you're from Google, then fuck you please uninstallrant please uninstall google fuck google mv google /dev/null sudo rm google sudo kill -9 google git rm google16 -
What happends when you leave your computer alone:
> sudo rm -rf /
P.D. If you don't what this command do look for it in google before running it on a linux system3