Re:Why Meteor will kill Ruby on Rails
by hyperbovine on Thursday October 31, 2013 @09:27AM
(#6646619)
FWIW Rails did not scale well during that time period. (One word: Twitter.) I don't know what the situation is like now but performance was a serious issue with rails in the early days.
What sites are going to have Twitter's scaling problems, though?
Re:Why Meteor will kill Ruby on Rails
by hyperbovine on Thursday October 31, 2013 @12:41PM
(#6647856)
Admittedly very few, although I did run into performance issues on Rails sites handling orders of magnitude less traffic. It's an interesting use case though -- tough to imagine a simpler web app than circa-2006 Twitter. Tellingly, they ultimately threw up their hands and moved it all to Scala.
Re:Why Meteor will kill Ruby on Rails
by kazagistar on Thursday October 31, 2013 @12:39PM
(#6647840)
And more importantly, I am pretty sure most startups would gladly have twitter's scaling problems in exchange for being the next twitter.
- it won't scale
- too much magic
- it's is too opinionated. Only good to do things one way
- it's ok. but only for toy apps
- I can do that easily in X framework, language (php, java, and now rails)
- these are just toy example. can you do anything "complex"
The author says this is significantly cutting down on his dev time. He also mentions how meteor reduces context switching when developing. IMO those are signs of a very promising technology. I don't know if meteor will become practical or popular. All I know is if works and it's stupid, it's not stupid.