collabs
Joined 8 months ago
Joined 8 months ago
There are optimizations possible like make segments smaller etc but the original algorithm is trivial. If we can't figure things out, we make segments longer and we slow down the trains until we can. I am positive for a sufficiently large track segment and a sufficiently slow train, we can always answer the question with a no.
I can't imagine how anyone can complain about this. The community revolted. The team listened. What else do we want?
I don't think that is a logical statement. Just something doesn't exist, does not prove that it can't exist. You need a stronger proof than that to show that in my opinion. At some point, you have to empower your users and trust them to do the right thing.
> 0.8 miles
Ok great I thought that I can walk...
however, it is actually 1.9 miles when walking according to Google Maps and the path lacks sidewalks.
This has become beyond ridiculous. I have personally gone from full support for Israel to now not even supporting Israel's right to exist. And I can't be the only one. I feel sorry for the (clearly increasingly rare) "normal" people of Israel but they will soon need to move out of Israel to not be bundled in with the crazies.
I don't think I would blame the environmental consultants though. This is just how we do things now.
The USD 2B path train stop at WTC became USD 4B+ and nobody went to prison for it. I don't think it should have even been USD 2B. All we needed was a path train stop.
Rocket trim is not street legal.
Once I could reach the actual engineering team to look at the internal tool to look at the bug I had to report though, they were very responsive. The tool for communicating was cumbersome and made me feel like a vendor / customer relationship even though you are supposed to be the same team but once they realized it was an actual defect and not some harebrained feature request, they fixed it relatively quickly.