pancrufty

I had no issues that were directly attributable to the way they behave and not to my own ignorance.

In short: once I learned and documented the checkout/update/reset commands, I was set.

The other “issues” were that they require extra config in some cases (CI), but again it’s just 2 lines in most cases.

You're using them wrong. I've been using them for years and I have no issues with them, however I treat them as a read-only dependency.

They have their use and it's not that hard once you figure out the exact sequence of git commands to use (but that applies to all of git)

As a non-American, the dumbest change that affects me daily, is the renaming of the master branch. Master means teacher in romance languages and its variations are part of daily usage. In git there's no "slave" part so it always meant "main" and not "owner"

It affects me daily because "look on master" became "look on the main branch" for no advantage to absolutely anyone.

European here: I do. I also have a federated government login that I can use to officially identify myself with the many government agencies.

I'm looking forward to the day physical mail is outlawed with few exceptions. Junk mail is such a wasteful endeavor only meant to subsidize shipments of value that can't be electronic.

I think browsers could nowadays figure out when enough bytes result in enough quality. Progressive images should have been the solution since the very beginning and it’s disappointing (yet expected) that they aren’t.

I really wish I could just point to the canonical source of an image and have the browser decide how much of is needed like it does for video segments.

Thumbnail: load 1000 bytes

Drag to desktop: download the remaining megabyte of your full-quality image

The current picture/sizes setup is a verbose joke hacked together because they refused to use progressive JPEGs for this purpose, which we had for a very long time. This whole thing could have been a single `<img progressive>` attribute

Uhm, this is a preview. You’re not supposed to use it until it’s widely available. They’re just showing it off and gathering feedback.

> I'll file this under something interesting to revisit in a year or two.

Correct. However things are moving fast so certain new features become widely available within months.

So verbose. Better:

  document.querySelectorAll('*').forEach(element => element.animate(
    {translate: '5px 5px'},
    {duration: 500, iterations: 1/0}
  ))

Except that rude words weren’t taped over back then, unless you lived in a monastery.

I think you can ask that to ChatGPT in a follow up question ;)

You can always press “cmd minus” to bring the old web back. Every press brings you back by a decade

> collecting users along the way to extracting money from them

Can you listen to yourself?

When was the last time you paid Node or npm inc? Projects have the absolute right to monetize without having to start that way. You can use bun without signing up, there’s no data, there’s no registration. There are only entitled users.

Same for my European bank. It’s annoying enough that I quit the app and reopen it to try FaceID again. I don’t even know my bank password

Selenium stinks alright