2 ms·
Go and Node were infants back then Java was (and still is) insanely heavyweight Ruby was tied to the hip with Rails despite being more than capable on its own
by nunez 4y ago
Go and Node were infants back then
Java was (and still is) insanely heavyweight
Ruby was tied to the hip with Rails despite being more than capable on its own and being much more expressive than Python (IMO). Python is faster though.
PHP was (and still is) PHP
- philsnow 4y agoRuby has Sinatra, which is much closer to Flask than to Rails.
- 0xFACEFEED 4y agoWe were shipping Go services all the way back in 2011! A bunch of my friends were working at other well known companies (of the time) and shipping Go stuff. Service based architecture was pretty popular and people were experimenting a lot. Walmart picked up Node.js in 2012. Not for their core stuff obviously but they were running a bunch of internal services with it. LinkedIn was evaluating it alongside Ruby (EventMachine) and Python (Twisted). They ended up picking Node for some of their services. Highly concurrent green-thread-ish type stuff was all the rage. Go and Node were the front runners. Python was the conservative choice. Ruby was hipster choice :P
- seanp2k2 4y agoLove Ruby method chaining and .tap(). Ruby was the language I could most “think in” and write a lot of stuff then have it just work like I figure it would. Python makes me roll my eyes having to explicitly handle a bunch of random small errors, like it’s being overly pedantic. I’m also not a fan of significant whitespace, which is another reason I prefer JSON to YAML (along with always having to look up if I need a hyphen on a line or not).