Re:MEAN Development Stack on Google Compute Engine
by eastbayjake on Thursday September 04, 2014 @12:42PM
(#8269260)
You can diss Mongo all you want, but you can't say Node.js is slower than PHP[1] or Rails[2] -- it's way faster.
[1] http://www.prahladyeri.com/2014/06/php-vs-node-js-real-stati...
[2] http://www.techhui.com/profiles/blogs/node-js-versus-rails-s...
Re:MEAN Development Stack on Google Compute Engine
by MrBuddyCasino on Thursday September 04, 2014 @01:10PM
(#8269416)
Thats what I was implying, sorry if that came across differently.
Re:MEAN Development Stack on Google Compute Engine
by eastbayjake on Thursday September 04, 2014 @01:54PM
(#8269654)
Apologies for misreading you! I can now see you meant that PHP and Rails are so slow that it's hard to be slower :)
Re:MEAN Development Stack on Google Compute Engine
by pessimizer on Thursday September 04, 2014 @11:48AM
(#8268924)
The concept is good, even though javascript is awful. I'm more in the direction of a Riak/Webmachine/Ember-Angular-Backbone-Batman-Knockout-Whocares/Erlang stack, though. There are many ways to execute pretty much the same thing as MEAN and avoid Node/Mongo, and new tooling on legacy projects to support the MEAN stack will inevitably also support other methods because that client-services model is so decoupled.
Can't be much slower than PHP or Ruby, so theres that. What is repelling to me is callback-hell and Javascript as a language in general. People will build simple stuff with this, then it will evolve, and then someone will have to deal with it. I don't want to be that guy.