4 ms·
I've got a completely data-free feeling that Ruby people hitting performance bottlenecks seem to reach for node whilst Python people have a tendency to look at
by andybak 13y ago
I've got a completely data-free feeling that Ruby people hitting performance bottlenecks seem to reach for node whilst Python people have a tendency to look at Go.
Does anyone else think that this rings true? And if so - is it a cultural thing?
- steveklabnik 13y agoThere are a _lot_ of Rubyists interested in Go, I'm not sure we can draw any real conclusions about the relative popularity of the move at this time.
- AYBABTME 13y agoI have the feeling that both camps are going for Go instead of Node. My only data-point is the shop I work for, and folks in the community that I know come from a Ruby background, such as Dominik Honnef, Ben Johnson, Mitchell Hashimoto.
- chc 13y agoMy impression is that people writing Web interfaces reach for Node while people writing CPU-heavy programs reach for Go. It so happens that Ruby people are more often writing simple Web apps while Python is somewhat more likely to be used for more computationally intensive tasks, but I think that's about as far as the correlation goes.
- bdcravens 13y agoI think that depends on whether they're more of a "Rubyist" or primarily Rails developers who know "just enough Ruby". I think Node (and especially a framework like Meteor or Express) is more approachable for those who spend most of their time in a framework like Rails.
- _random_ 13y agoJavaScript people go for Node.js - they have nothing to loose.