kamen

It’s not even that much of a pain. I’m mostly dealing with TypeScript, very rarely vanilla JavaScript, and it’s even enjoyable most of the time.

Eh, whatever. It puts food on the table…

Yes, indeed, I see javascripts in the wild every day.

“Catching mice is a stupid question.”

This must be a “hold my beer” kind of joke and someone wanting to see how far they can take it.

Weren’t you getting runtime errors for the function not being found?

Yes, and there’s that small thing that’s done in a slightly different manner that you can’t change through settings and it messes with your muscle memory.

Same.

No, we must rewrite it in this fancy new framework that came out last week.

(/s if not obvious)

I have the equivalent of RAID 5 too, but mind the usual “RAID is not a backup” - if you deliberately delete something (or something goes wrong with an app managing your media), hardware redundancy won’t save you in any way; it only helps if the data is intact and you want to remedy a hardware failure.

I only back up my music collection because I put extra effort into organising and tagging everything, plus some of it is rips of CDs not available anywhere. As for movies and TV shows, I only back up configurations and catalogues of the relevant apps, the contents themselves are 1) too big to be feasible to back up and 2) 99% of the time available to re-download.

Imagine playing a shooter over a network using this protocol.

My take is use a GUI for anything read-only/nondestructive (i.e. anything that won’t modify your local or remote state). It’s nice for example to compare the state of two branches.

For anything that does changes make sure you know what’s happening under the hood, otherwise you might shoot yourself in the foot. It’s convenient for example to do a commit and push in one go, but then you lose the ability to edit any changes (you’re forced to either do another commit, or change your local commit and force push).

In VSCode you can go to the Output pane and switch to Git - there you’ll see everything that gets done through Git’s CLI for whatever you do through the GUI (although it can be a bit noisy); same goes other GUI utils.

One key thing that can help you wrap your head around rebasing is that branches get switched while you’re doing it; so, say you’re on branch feature and do git rebase master, for any merge conflict, whatever’s marked “current” will be on master and what’s “incoming” is from feature.

There’s also git rerere that should in theory remember a resolution you do between two branches and reuse it every time after the first; I’ve rarely used it in practice; it would happen for long lived branches that don’t get merged.

This is now the correct database.

“We conform to the open standard, but only to the parts that we like”

Still worth it if you learn something from them, even if that something is that they suck.

Wow, that’s pretty terrible. I can’t remember the last time I’ve seen data caps on home Internet (edit: there were some a while ago, but those were basically cellular-at-home for places that are hard to reach with copper or optic fibre); must’ve been early 2000s. Right now I get 600 Mbps d/400 Mbps u at home and 10 Mbps d/u cellular (no data cap) for a total of under 30 EUR/mo.

Imagine Copilot using it to intentionally showcase terrible code.