3 ms·
I'm not surprised, the whole language (Ruby) and ecosystem favors "ease of use" (ie the ability to write code fast) over correctness in so many places. Subtle d
by jupp0r 2y ago
I'm not surprised, the whole language (Ruby) and ecosystem favors "ease of use" (ie the ability to write code fast) over correctness in so many places. Subtle details that other languages would require you to handle in order to robustly handle non happy path conditions are often ignored, lumped together, return just nil, etc. It seems careless, but a large group of engineers love it because it gives the illusion that the world is simple.
- neonsunset 2y agoRuby is not alone in this. Go shares similar philosophy to just half-ass the implementation. Well, at least it's not as brittle and impossibly slow as Ruby.
- jupp0r 2y agoDo you have an example? My impression of the Go standard library is that they picked a pretty decent compromise of abstraction levels over the various OS facilities they use under the hood.
- wk_end 2y agoThe classic reference here is “I want off Mr. Golang’s Wild Ride”: https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-...
- jupp0r 2y ago"Ruby is not alone in this" Agreed. My point was rather that this is not Ruby's only dangerous shortcut.
- byroot 2y agoIf you read TFA, you'd have seen this problem isn't exclusive to Ruby at all, several other languages have a similar API.