3 ms·
It's definitely a trade-off. What Node gives you is async when you need it at the cost of giving you async even when you don't. The pain and constraints introd
by rmgraham 13y ago
It's definitely a trade-off. What Node gives you is async when you need it at the cost of giving you async even when you don't.
The pain and constraints introduced by this forced use of async sure has spawned a lot of wheels of all sizes, colours, and compositions.
- sync 13y agoThere's always `fs.readdirSync` etc. node isn't forcing async on you, especially when it comes to file handling.
- jerf 13y agoRuby is the wrong comparison. Write that same code in Go, suitably translated, and it would be fully "async". I hit Go just because it's the most Algol-ish of the sane languages. There's several other options where you just write the code and the compiler and runtime do the async for you.