3 ms·
To draw an analogy, whether server-side/client-side JavaScript frameworks will become the next RoR is like guessing whether Facebook will ever be able to moneti
by bialecki 14y ago
To draw an analogy, whether server-side/client-side JavaScript frameworks will become the next RoR is like guessing whether Facebook will ever be able to monetize the way people think it might. It seems like it should be possible, but it doesn't seem like there's an obvious way forward. </bad-analogy>
I love JavaScript (in the weird way everyone who "loves" JS, loves JS), but I'm skeptical the next big web framework will be written in it. I want to believe, but it just doesn't feel right yet. I hope it will and I can't wait for the "ah ha" that makes it feel right. But it doesn't yet.
- firefoxman1 14y agoWhile I think Meteor and Derby are moving more in the right direction than Express, I think if any of these frameworks want to be the Rails of JS, they need to play on the strengths of Node much more. Node really shines when it has to serve a ton of small data, rather than render CPU-intensive templates on the server-side. Express treats Node as if it were Ruby or Python too much. I feel like Meteor is completely missing the point when they do things like use fibers. To be the go-to Node framework, it's going to have to move much more client-side, but still make it easier to build an app than something like Restify.