> I am quite alienated by the hype and the completely exaggerated promises
And yet here you are writing a post that does that about a different technology. Not exactly the approach I’d expect from a senior engineer.
The individual you responded to did a great breakdown of the bias in your article. You should take it in to account rather than reject it, especially if you want to convince people.
> you are writing a post that does that about a different technology
No, I report based on my experiments and realistic expectations. I don't promise: "just rewrite in Rust and everything is safe, and don't hesitate to spend millions for it". I offer a perspective instead based on proven track records of the technology and present a method how to make it better accessible.
It’s a site where programming nerds congregate to waste time arguing with each other. Where do you think you are?
This same pattern used to play out with Ruby, Lisp, and other languages in different eras of this site. It will probably never stop and calling it out seems to just fan the flames more than anything else.
Eh, the Portland - Seattle - Vancouver BC Amtrak sector is also pretty usable. In practice I've found it's not substantially faster or slower than driving - at least not enough to make a big difference for me.
On a train I can read a book, eat some food, drink, stare at the scenery, check my phone, no problem because I'm not driving. On most trains a professional is driving, on a few a machine is driving, but either way it's not my problem.
Pretty, yes, but geopolitical issues slow the service. We were at least two hours late thanks to various issues with crossing the border and fitting in with the cargo trains.
Stuff going back some ~20 years, along with photos ("Instagram-like") and videos (mostly my motorsports stuff).
reply