Spyke

Replies

Comment on

Books are generally better

Reply in thread

Hot take, the battles in the book aren't great because Tolkien doesn't want to glorify violence. Half of the fights are like two pages in the books before the point of view character passes out. After realizing that I was kind of disappointed in how "campy early 2000s action movie" the battles in the films are.

fuck_ai

Comment on

there is a AI free fork of vim, called evi

Reply in thread

I'm sad I hate to scroll this far to see a sane take. Bad code is bad, AI accelerating the destruction of the planet is bad, but experienced maintainers using the tools that exist is not bad, and trying to fork a project like Vim because of that is insane. Power to them if they actively maintain it, but I don't see that in the cards.

Comment on

Cloudflare to AI Crawlers: Pay or be blocked

Reply in thread

iirc it came out that the gambling site was intentionally cycling through cloudflare's IP range to avoid IP blocking, causing legitimate websites to be flagged as unsafe. They said they'd still host them, they just need their own IP and not one of cloudflare's. Horribly communicated to the customer though

Comment on

Orwelluan

Reply in thread

wrt conf file location, they're only generally in /usr/lib/systemd, /etc/systemd, or /run/systemd. You can always find out what's getting read with systemctl cat <service-name>. Way easier to find stuff than with some other random programs imo, I've seen crap have default conf files in dumb places like /usr/share/<service-name>/lib/etc.

Comment on

Vim > VSCode

Reply in thread

Like, a GUI plus command line, objectively provides you with more UX tools and ways of presenting data and interactions to the user

My long list of vim plugins and adhoc macros would like a word. I don't doubt VSCode can do something similar, but I love that I can script vim to do basically whatever. Also, it feels much faster to not need to touch a mouse at all.

Comment on

Well well well.

Reply in thread

Fun fact! If you added a file but never committed it you can still recover it with git fsck --lost-and-found. The changes were still added to the git object store, and by grepping through the dangling blobs you can find the object containing the changes you care about.