4 ms·
It really comes down to whether you view HTML/Javascript as source code or object code. If HTML&JS is source code, you ought to keep it clean and minimal. You'
by mcav 17y ago
It really comes down to whether you view HTML/Javascript as source code or object code.
If HTML&JS is source code, you ought to keep it clean and minimal. You're betting that browsers will evolve to include desktop widgets and other aspects of the "native" experience in HTML tags and Javascript APIs.
If HTML&JS is object code, you're rooting for abstractions over HTML and Javascript, so that HTML/JS becomes assembly language.
I don't mind the extra abstraction. But it's unfortunate that we're adding so many layers of abstraction over a system that wasn't really designed to be used that way.
- cpr 17y agoIt's a little early to tell for sure, but it might well be A Great Thing for JS+HTML/CSS to become the assembly language of the web. If Javascript engines get faster, and CPU speeds keep slowly inching up (looks like Moore's Law has temporarily been repealed ;-), and things like Web Workers become commonplace, ...
- amadiver 17y agoI'm curious as to why you feel it's unfortunate to add so many layers of abstraction over the system. Besides the "All abstractions are leaky abstractions" argument, is there any other reason you feel like this is a bad thing? Or is it ruffling your engineering feathers?
- mcav 17y agoPrimarily because it's an inefficient abstraction. Yeah, Moore's Law and all that. But still.