33 ms·
(how many different times are we going to create a new Web framework, guys?) As many as it takes. How many times are we going to build a new house or bridge?
by batista 15y ago
(how many different times are we going to create a new Web framework, guys?)
As many as it takes.
How many times are we going to build a new house or bridge? How many times are we going to write a new love poem?
It's not as if we are anywhere near already having made the best web framework that can be. Not even close (include Rails, Seaside, Lift, whatever...).
Where is the WCFs, the WPFs, the Silverlights, the things that would get us fired up?
WCF, WPF and Silverlight are things "that would get you fired up"? Seriously, man?
And as much as this is going to probably just throw fat on the fire, all the excitement around JavaScript as a language reminds me of the excitement about Ruby as a language. Does nobody remember that Sun did this once already, with Phobos? Or that Netscape did this with LiveScript? JavaScript on the server end is not new, folks. It’s just new to the people who’d never seen it before.
LiveScript was useless and never got any wide adoption, and it's nothing like Node.js besides both making use of js server side. At the time, javascript was a joke, fragmented, language and was not used on the front end that much, except for small pieces of dynamic functionality. There were also no AJAX and no JSON. so having JS on the server had nowhere near the convinience and code re-use value that having JS on the server does now.