"JavaScript is there to decorate HTML, not the other way around."
Would it be fair to say this is a subtle jab at JavaScript used on the server side, namely what nodejs is doing?
Q&A with David Heinemeier Hansson
11–20 of 20 posts
Re: Q&A with David Heinemeier Hansson
#12"JavaScript is there to decorate HTML, not the other way around." Would it be fair to say this is a subtle jab at JavaScript used on the server side, namely what nodejs is doing?
No, it's a jab at client-side frameworks like Angular and Ember.
Re: Q&A with David Heinemeier Hansson
#13"JavaScript is there to decorate HTML, not the other way around." Would it be fair to say this is a subtle jab at JavaScript used on the server side, namely what nodejs is doing?
Digging for controversy? He's pretty opinionated on where he feels JavaScript fits into the stack. Should be completely expected coming from the creator of a server side framework.
Re: Q&A with David Heinemeier Hansson
#14>JavaScript is there to decorate HTML, not the other way around. Does that mean that HTML is not there to decorate JavaScript? Or is he dinging Backbone and the other JS MV* frameworks cropping up.
The latter.
Re: Q&A with David Heinemeier Hansson
#15I'd be curious as to exactly what features comprised the first released version of rails. Was it originally in the MVC structure we know today, or was it more a mixture of random parts that were refactored into that later? Did it use a CGI model, or did it embed webbrick from the start? etc.
It wasn't terribly different. Old apps are still recognizable as rails. It is just more polished now, and a few head scratchers have died off like RJS and components, and a lot has been refined. The biggest differnces are probably the asset pipeline, bundler, and UJS. Production hosting was an absolute nightmare. I never did understand it. Thankfully, it got better quickly.
Re: Q&A with David Heinemeier Hansson
#16Re: Q&A with David Heinemeier Hansson
#17Re: Q&A with David Heinemeier Hansson
#18"JavaScript is there to decorate HTML, not the other way around." Would it be fair to say this is a subtle jab at JavaScript used on the server side, namely what nodejs is doing?
No, he means the application logic should be on the server side, not in the browser. I doubt he has a problem with server-side Node.js.
Re: Q&A with David Heinemeier Hansson
#19I wonder what his opinion about Functional Programming is.
Re: Q&A with David Heinemeier Hansson
#20Earlier quoted context omitted.
The latter.
Conflict of interests. The server side is dying.
This oscillates back and forth: we're never going to get rid of one side so it's pointless to start claiming the world has changed when a 60-40 split flips.
As an example: all of the apps which still work if anything, anywhere, doesn't load and run a huge pile of JS correctly. c.f. Twitter, Gawker, etc. The client side is fragile to an extent which simply isn't true on the server – this doesn't mean you don't use it but rather that you still have to think about what happens when something breaks.