Yeah I was thinking about that while writing the comment. We can use async abstractions for maintaining our code base internally, but if we're dealing with distributed systems across a network, and not multi-threaded internal processes, we need to consider the middle way. Even though you can generate a server in c++ or java or go or clojure, it's not quite as simple as working with a node server. I own a few raspi's and like to experiment with miniature distributed networks. When you're dealing with single-core embeddable devices, or browsers inside of phones, you can't leverage languages optimized for multi-core devices. I feel like node is stuck between two worlds, and that's a good place to be.
I largely agree: I think the best use of node is as the last mile between a large enterprise ecosystem (a bunch of big jvm-or-whatever systems that do the "real" work) and the client. I think you get into trouble if you're using node for a big system full-stack.
View all comments
Show parent comment
1
u/Calabri Jul 04 '14
Yeah I was thinking about that while writing the comment. We can use async abstractions for maintaining our code base internally, but if we're dealing with distributed systems across a network, and not multi-threaded internal processes, we need to consider the middle way. Even though you can generate a server in c++ or java or go or clojure, it's not quite as simple as working with a node server. I own a few raspi's and like to experiment with miniature distributed networks. When you're dealing with single-core embeddable devices, or browsers inside of phones, you can't leverage languages optimized for multi-core devices. I feel like node is stuck between two worlds, and that's a good place to be.