3 ms·

> Imo in Ruby it's not that common that service calls are deeply nested. In frontend it's opposite. Components are very nested This feels like the answer that

> Imo in Ruby it's not that common that service calls are deeply nested. In frontend it's opposite. Components are very nested This feels like the answer that makes the most-ish sense, although I've worked with a ton of nested Ruby code as well. My suspicion on why people use Typscript is that it's is more about the tooling than types. In Ruby or Python, I can drop into a REPL anywhere in the code and be in context of what I'm trying to do, but that seems way less common in Javascript. Perhaps because of the async nature?

wrestlerman 8y ago
Tooling, that means? I haven't had an opportunity to work on a big/very-big JS project yet. But from experience based on working on small-medium size JS project, I guess console.log() and refresh is just enough. After thinking about it, I guess readability is a huge part of it, there are lots, lots of JS packages. And it makes sense for them to be readable, so they could be easily updated by new contributors to remain valid. Personally, I have really hard time contributing to gems, because of so much metaprogramming in them, I don't feel like spending a week to understand what is connected with what and if my changes can break it.