My world simultaneously viciously hating Arch when something breaks, then absolutely loving Arch, then hating it again when something breaks, then loving it again
I had haddock, white wine and gala apples once, and asked ChatGPT to make me a slow cooker recipe. The results were... Surprisingly not bad. I don't think I'll ever do it again though.
That's me when my family wants me to whip up a random pasta lunch. Hmm, mulled black peppercorn and garlic? A bit of paprika? Tomato paste, oh now it definitely needs oregano.
I was on EndeavourOS for a couple of years and now I'm just on vanilla Arch with KDE and I also couldn't imagine just dumping all of my knowledge and problem solving workflow by jumping to a different distro or architecture. I certainly can't see myself ever using Windows again. It's very weird to imagine that if I ever wanted a flagship computer I would probably buy an Apple.
GPT was super useful for me getting into programming with very basic, core shit that it basically couldn't get wrong. But now that I'm learning how to actually program in C it is practically useless. It makes so many mistakes so often
/./ would apply to the current directory, and /../ would move into the parent directory. I imagine the idea is to start in a deeply nested directory, /home/user/Documents/old and begin either maintaining the directory (in a sense doing something like '–0' or reverting to a more basal directory (alla '–1'). The branch moving into ~/Music/badSongs is probably a way of trying to disguise the intent of parsing /.././.././.././.. to root and then /* to glob all root directories.
I imagine if for some reason ChatGPT was running Zsh or something that supports that kind of augmented Bash syntax it would work, but realistically it likely would fail.
I think someone might have better luck by attempting to rm - rf --no-preserve-root with a series of random, less-necessary files and throw a /* in the mix. Or attack another important directory that might get overlooked like /proc/*
I noticed recently that a Linux command mentioned in its manpage that it supported Q as a bit prefix and I had to stop to ponder the utility in encoding a million-billion Terabytes.
At least they had company for ten years