16,544 karma · joined April 2, 2010
Last time I saw a TÜV report it was that electric cars show up with a) rather little service checks in between and b) they are too heavy for the axels and that causes wear compared to a regular car.
A 200 sqm apartment in Vienna, mixture of think walls and drywall. The signal goes everywhere with three well placed mesh things.
We have about ~100 devices connected to our home network according to my router and other than 6 devices, they are all on Wifi. I would never have expected that, but the reality is that it just got so much better over the years that I cannot be bothered with actually wiring things up any more.
That's in part because the outlets are not necessarily aligned well with the devices that would need to be connected, and then all kinds of other shit that is going on with home ethernet.
In 2020 I wrote about my USB-C adapter breaking ethernet [1]. It is still one of my most read blog posts and I get emails from it still, because apparently even in 2025 actually hooking up a USB-C ethernet adapter will cause quite a few switches to fail.
Long winded way of saying: our Ethernet does Gigabit because I never upgraded and has almost no devices left. Our Wifi does >4Gitabit because it was easy to swap and most devices are Wifi anyways.
It's just a question of political will
You don't need to introduce capital controls to make it unattractive to invest in the US. There are plenty of options that the EU could pull that would make investments abroad very unpopular quickly.
You might not find it ambiguous but it is ambiguous and there were attempts to fix it. You can find a warmed up discussion about this topic here: https://mailarchive.ietf.org/arch/msg/dnsop/2USkYvbnSIQ8s2vf...
I can build my own curl in a week, but the value that curl gives me is that it's a multi decade old library, by a person that has dedicated his live to keeping the project there, keeping a quality bar etc.
The value of curl is not curl, it's the human behind it.
At the very least because it's now human + coding agent, separating out the human input from the machine output in pull requests becomes necessary in my book. There are dramatic differences in prompting styles that can have completely different qualities of output and it's much easier to tell it apart from the prompts than from the outputs given that it's basically an amplification problem.
I'm basically saying this except I currently don't give the agent a tool yet to do it automatically because it's not really RL'ed to that extend. So I use the branching and compaction functionality of my harness manually when it should do that.
> If you mean manually, that's still interesting, but that kind of feels like the same thing to me.
It's similar, but it retains the context and feels very naturally. There are many ways to skin the cat :)
The token are not wasted, because I rewind to before it started building the tool. That it can build and manipulate its own tools to me is the benefit, not the downside. The internal work to manipulate the tools does not waste any context because it's a side adventure that does not affect my context.
My agent writes its own glue code so the benefit does not seem to really exist in practice. Definitely not for coding agents and increasingly less for non coding agents too. Give it a file system and bash in a sandbox and you have a capable system. Give it some skills and it will write itself whatever is neeeded to connect to an API.
Every time I think I have a use case for MCP I discover that when I ask the agent to just write its own skill it works better, particularly because the agent can fix it up itself.
It was a good intention, but the ramifications of it I don't think are great.
The amount of custom stuff I needed to add was minimal (just mostly ensuring that if network is gone, it falls back to native navigation to error out).
Examples: https://lucumr.pocoo.org/ and https://dark.ronacher.eu/
I also found Claude to be excellent at understanding HTMX so that definitely helps.