Oh my, you should have tried to integrate with Google Prism. That was a madness! Nano Banana was just a little tricky to set up in comparison!

One needs to be rally dumb to buy a smart fridge

If only it was supported by Gui tools... I don't bother use Git from my terminal, but use GiFork instead. As I understand there is nothing that may be interesting for me in my scenario...

I actually find I don't need to use any GUI tools with jj because I can actually understand what's going on under the hood since the mental model is much simpler. It helps that jj has excellent visualizations straight in the terminal.

Not as bad as their payment provider. So many problems... One of the worst integration I've ever seen. But who knows, maybe it was generated by their chat. That would explain a lot.

The Nazis are in US now....

It seems that this was a very cold and unexpected shower for all of us in Europe (maybe except Hungary) and now there is a big focus on working together against our common enemy and finding other more reliable partners. It's a pity we were relying this much on Americans for so long... Now we have motivation to change approach. And do it fast!

Only 400?

But to be honest the UX of Mastodon is just unusable. Following someone is not a click on Follow button. It's the most basic feature I can think of. And it's complicated there. It just couldn't work. Bluesky just did it better.

I agree that the UX of Mastodon was not the best. I tried several times to use it and it just never "clicked". Bluesky just worked for me, almost without trying.

Maybe my problem with Mastodon was choosing the server to join. My brain knows that it's federated and it really doesn't matter which server you choose. However it always felt like I was choosing the wrong server somehow. Just that little bit of friction was enough to drive me away.

If OP wanted to shrink nom packages then npm could introduce two types of npm package - the build package and source one. This way a lot of packages would be smaller, because package code could be safely distributed through a separate package and not kept in the build package. There are a lot npm packages that explicitly include whole git repo in the package and they do so because there's only one type of package they can use

Derisking changes may not work sometimes. For example I don't use Spotify anymore, because of their ridiculous Ab tests. In one month I saw 3 totally different designs of the home and my fav playlists page on my Android phone. That's it. When you open Spotify only when you start your car then it's ridiculous that you can't find anything and you are in a hurry. That was it. I am no longer subscriber and a user of this shit service. Sometimes these tests are actually harmful. Maybe others are just driving and trying to manage Spotify at the same time and then we have actual killed people because of this. Harmless Indeed.

Ever tried a support call helping someone using a website that has A/B testing on? It's a very frustrating experience where you start to think the user on the other side must have mistyped the url. A lot of time wasted on such calls. And yes, the worst is when these things only happen in things you use only when in a hurry.