> Who needs a JavaScript date picker?
> The answer, in most cases, is nobody!
I tried some of the inputs and found that they worked well for initial input, but editing inputs didn't (e.g. the masked date input cursor just jumps over previous decimals, when typing a new number)
I made a reproduction video and tried to report it to the Pikaday issue tracker after which I found out it's deprecated.
Going back, and comparing the readme with the page, does show that the post uses native inputs. ... I feel that could have been more explicit; in this post I expected Pikaday to have the option to use native pickers with some component styling.
For example, the title "Impro: Improvisation and the Theatre" by Keith Johnstone, linked by another article posted to HN today gives back the following suggestions:
- Truth in Comedy: The Manual of Improvisation by Charna Halpern - Steve Jobs by Walter Isaacson - 1984 by George Orwell - Harry Potter and the Sorcerer's Stone (Harry Potter, #1) by J.K. Rowling - Sapiens: A Brief History of Humankind by Yuval Noah Harari - The Alchemist by Paulo Coelho - The Tipping Point: How Little Things Can Make a Big Difference by Malcolm Gladwell - Dune (Dune, #1) by Frank Herbert
It's a bit unfortunate that all suggestions are fairly popular titles, which are fairly easy to find, while the unpopular or niche may be just as well written but a lot harder to find.
Within niche topics or books, it is also usually harder to provide multiple similar enough titles up front.
https://nltimes.nl/2025/10/29/ns-hit-microsoft-cloud-outage-...
It should be noted that the article isn't complete: while the travel planner and ticket machines were the first to fail, trains were cancelled soon after; it took a few hours before everything restarted.
Based on what the conductors said, I would speculate that the train drivers digital schedule was not operative, so they didn't know where to go next.
“Flexible” means the range from gradual typing (‘any’) to Turing complete conditional types that can do stuff like string parsing (for better or for worse). Structural typing vs instanceof and so on.
There’s really no comparison between Typescript’s type system and Rust’s. It’s worth noting though that Typescript is a bolted on typesystem that has explicitly traded soundness for flexibility. That’s the real tradeoff between Rust and TS IMHO. Rust is sound and expressive but not flexible, while Typescript is expressive and flexible but not sound.
Worse, typescript may even run out of it's allocated memory sometimes.
Here in The Netherlands, almost all trains were first delayed significantly, and then cancelled for a few hours because of this, which had real impact because today is also the day we got to vote for the next parlement (I know some who can't get home in time before the polls close, and they left for work before they opened).
I remember I at one point had expanded enough menus that it covered the entirety of the screen.
Never before have I felt so lost in a cloud product.
I never understood why a clear and consistent UI and improved UX isn't more of a priority for the big three cloud providers. Even though you talk mostly via platform SDK's, I would consider better UI especially initially, a good way to bind new customers and pick your platform over others.
I guess with their bottom line they don't need it (or cynically, you don't want to learn and invest in another cloud if you did it once).
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.