Debian Testing.
Learning about the xz backdoor was a fun week.
Debian Testing.
Learning about the xz backdoor was a fun week.
"Stop doing what I told you to do and start doing what I want you to do!" has been uttered in my office a few times.
I'm a software developer. My default explanation to people who don't know what that means is, "I whisper to computers, and sometimes they do what I ask".
Either:
My money is on the former.
I would say the defining characteristic that sets Breath of the Wild apart from its contemporaries is its "chemistry engine", as they call it. That meticulously programmed system of interactions where absolutely everything in the world affects everything else in ways that are intuitive. Wooden objects burn, lightning strikes metal things, fire will melt ice, electrified objects will conduct through metal and water, etc. That, in tandem with its cel-shaded artstyle, minimalist piano flourish soundtrack, and general lonely, somber vibe in a mechanically lush but socially empty world. That's the identity of BotW.
I haven't played Genshin Impact so I don't know how deep the similarities are. It sure superficially resembles BotW if you squint and look at it from a distance. Big open world, vibrant cel-shaded graphics, live in-overworld combat, you can climb walls and soar with glider physics, they got the high fantasy plus inexplicably advanced magitech thing going on... definitely some marks on the bingo card, but not really things particularly unique to BotW, either. I have no idea how much Genshin Impact actually resembles BotW up close.
Surprised how, of all the people who took the bait, not a single one of them complained about systemd.
My beard isn't long enough to have an opinion about systemd. All I know is all my homies hate systemd for some reason.
The other day I learned that you can just grep an unmounted filesystem device. It will read the entire disk sequentially like it's one huuuuge file. And it will reveal everything on that disk... whether a file inode points to it or not.
Used it to recover data from a file I accidentally clobbered with an errant mv command. It's not reliable, but when you delete a file, it's usually not truly gone yet... With a little luck, as long as you know a unique snippet that was in it, you can find it again before the space gets something else written there. Don't even need special recovery tools to do it, just use dd in a for loop to read the disc in chunks that fit in RAM, and grep -a for your data.
Stop threatening. Commit. Take the leap. A lot of us here are already on the other side and we'll help you find your footing.
Should I tell them about the drive thru liquor stores?
I mean, yeah, kind of. In the same way pilots fly planes out of a stubborn sense of pride for knowing what all the flight deck controls do.
I thought his name was Alec, not Alex.
The primary thing I hate about them is that every snap package appears to your system as a separate mounted filesystem. So if you look in your file explorer, you can potentially see dozens of phantom drives clogging up your sidebar.