As someone who fairly often travels by German ICE (not their regional trains), I've only ever experienced the timetable unreliability.
WiFi is fairly reliable and much much better than for example the Dutch railway (NS) WiFi which never seems to work, and I can't remember the last time it didn't work on an ICE. I've never had any seat reservation mix ups or (knowingly) missing train cars; the last two I've experienced only once in Europe, on a cross border train from Slovenia to Austria, with the seat booked via the ÖBB on a Slovenian train.
When these ICE's are on time and show up, I like them a lot. The seats are very comfortable, there's food service in the train, the seat reservations aren't thát high, and are optional (unlike say high speed rail in Italy, where there's a 15 euro required seat reservation on top of the ticket price), the staff is consistently friendly and so far (I think) they haven't joined the annoying recent trend to put digital ads on the same monitor as the in train timetable.
More so, I really really like the Deutsche Bahn app and use it for trains all over Europe.
Reading this article makes me ask myself if the route and type of train matters, but also that the article didn't really add anything new from what wasn't already known. With their ongoing frequent delays DB made them an easy target for anything under the sun, but comparatively to other trains in Europe, at least for DB ICE's, delays aside, I feel they're doing quite alright.
Python is the primary implementation, Java is there, Go is relatively new and aiming for parity. They could have contributed the Typescript implementation and built on common, solid foundation, but alas, the hydra's heads are not communicating well
These other "frameworks" are (1) built by people who need to sell something, so they are often tied to their current thinking and paid features (2) sit at the wrong level. ADK gives me building blocks for generalized agents, whereas most of these frameworks are tied to coding and some peculiarities you see there (like forcing you to deal with studio, no thanks). They also have too much abstraction and I want to be able to control the lower level knobs and levers
ADK is the closest to what I've been looking for, an analog to kubernetes in the agentic space. Deal with the bs, give me great abstractions and building blocks to set me free. So many of the other frameworks want to box you into how they do things, today, given current understanding. ADK is minimal and easy to adjust as we learn things
Here’s how Nano Banana fared: https://x.com/danielvaughn/status/1971640520176029704?s=46
Also my bet would be that video capable models are better at this.
Of course they are.
> As long as the inference is not done at a loss.
If making money on inference alone was possible, there would be a dozen different smaller providers who'd be taking the open weights models and offering that as service. But it seems that every provider is anchored at $20/month, so you can bet that none of them can go any lower.
There are! Look through the provider list for some open model on https://openrouter.ai . For instance, DeepSeek 3.1 has a dozen providers. It would not make any sense to offer those below cost because you have neither moat nor branding.