4 ms·
Really? Personally, I've always enjoyed writing services with high I/O and low computation in Node.js. I usually consider Node.js first when having to create a
by lovingCranberry 4y ago
Really?
Personally, I've always enjoyed writing services with high I/O and low computation in Node.js. I usually consider Node.js first when having to create a new REST API (which usually just gaps between http and the database) or websocket server.
- john567 4y agoDepends on your use case but unless you really need JavaScript interop I think there are better alternatives. You are of course free to do whatever but neither JavaScript or Node is the answer to everything. I think the Go concurrency model is a lot nicer, and it's considerably better throughput wise. As much as I enjoy writing JavaScript is riddled with stupid stuff and lack sensible primitives but I do care about computational performance because I have a lot of code that I want to optimize and towards that goal JavaScript and V8 gets in the way. Even if it's a good VM it can get really ridiculous from a performance point of view.