3 ms·
>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 th
by crisnoble 13y ago
>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.
- dchuk 13y agoThe latter.
- smrtinsert 13y agoConflict of interests. The server side is dying.
- rhizome 13y agoDid you not live through the thin- vs. thick-client wars of the 90s? It's an ever-swinging pendulum.
- acdha 13y agoThis 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.