Meh, the threat vector to me as a resident of Germany is the German government - not some dude at the other end of the world. What is Musk going to do? Ban me from Twitter? Not sell me a Tesla?

That's nothing compared to what German authorities can do to me. Germany is a country where you get police searching your home for torrenting movies or making stupid jokes on Facebook. So yeah.

Also about enshittification - one could argue that our local ISPs never left that phase to begin with.

He could just turn off Starlink in Germany. And yes, German ISPs suck donkey ass.

He could sell information about which websites you visit.

So can every website with a tracking cookie

Only for that website.

>Regardless of who is at fault, you are losing a lot of customers that way.

Don't know. Germans are stingy. I'm German, I live in Germany yet I don't even localize my software to German anymore because German downloads wouldn't convert in any meaningful way. (Even when I had German localization).

It's just anecdotal of course but every other dev I talked to would confirm this unless they had some very germany-specific product.

I'm glad Vodafone is available where I live. They're not better but at least they're an alternative. Also Telekom manages only to deliver 250mbit/s while Vodafone gets 1gbit/s.

Last apartment I rented Telekom was the only option and that was one of the reasons why I decided to move.

Starlink I would love to try but as there's building and trees blocking the horizon it's not an option here sadly.

Not an alternative anymore. Vodafone started doing the same shit with their peering at the end of last year.

Both throttle in my area unless we vpn so I just share a vpn with a friend to fix it.

Vodafone seems also terrible, but maybe better than DT?

I have the same problem with Jekyll. I fixed my website for the Jekyll version I installed when I got this machine (in 2021). I dread the moment when I get a new computer and have to either try to install this particular version of Jekyll or to fix my website again.

I just assumed static website generators would be stable but well, there's always something that breaks. Terrible user experience for someone who just wants to use the generator to generate a website vs. to tinker with it as a hobby.

I'm in the process of porting my website to PHP ... but that project hasn't gone anywhere because currently everything works ;)

In retrospect, Jekyll has been relatively stable recently. The last stable release was in January 2025, v4.4.1[1].

I've been using 4.3 to 4.4 without much issues, granted the sites I generate are simple.

[1]: https://jekyllrb.com/news/

Download links are here: https://archive.org/details/utah_unix_v4_raw

That's certainly a (to me) very unusual way to learn programming.

It’s not about learning programming, more about learning how to solve leet code problems quickly as I understand it

Before macOS 26 I would have agreed with you. But after Tahoe my M1 MacBook Pro feels a lot slower.

Funny, there's even some regression in layer backed NSView rendering where the app I'm working on is faster (in some aspects) in a macOS 15 VM than on bare metal under macOS 26.

Are you running any electron apps that have not yet been updated to use the most recent upstream electron?

https://furbo.org/2025/10/06/tahoe-electron-detector/

I've got a couple things that I use which aren't yet up-to-date, and are blocking my upgrade.

I've got one of those in my 2004 Mazda. It even came with a backup camera. Best 50 Euros ever spent. :)

I got one too... the camera is still up on my bookshelf a year later.

Heh, funny. I recently implemented a countdown for a teleprompting app and that's exactly what I ended up doing to make the countdown "feel right".

The countdown in question doesn't display fractions of a second so it would immediately switch from "5 seconds left" to "4 seconds left" which just doesn't feel right. Adding 0.5s solved the issue.

Just round up. The countdown is done as soon as 0 appears (0 doesn't linger for 1 second).

To expand a bit on what others have said:

If you're counting up, round down. If you're counting down, round up. A human expects the count to finish at precisely the moment we get to the last number in the sequence (zero, for counting down). Do a count in your head to see what I mean.

Apple chose a compromise by rounding to nearest, for it to "feel good", but you lose the ability to exactly predict when the timer ends as a human. Typical Apple.

the comments/replies to his tweet remind me why I usually avoid twitter