3 ms·
The primary problem with web development is not that javascript, css, DOM and dynamic HTML make for painful application development, even though that is the cas
by abdulhaq 15y ago
The primary problem with web development is not that javascript, css, DOM and dynamic HTML make for painful application development, even though that is the case. The main problem is having divergent implementations of HTML/DOM etc.. that results in having to test and maintain code for a dozen different browsers/versions. Google adding yet another language to the pool just adds to this problem.
- bphogan 15y agoExactly. Especially if it's a server-side language. I'm really hoping that we're coming to the end of the era where we use server-side languages to generate static HTML, and I hope we're closer to the end of the creation of new languages to do that. That problem is solved. What's not entirely solved is how we make client-side interaction with server-side systems work better. Backbone.js + Sinatra is a nice start, but then you have browser inconsistencies and awful client-side debugging. I'd love to see people tackling that problem instead of inventing Yet Another Framework, But then, maybe Dart is something client-side. Of course, then only Google's browser would support it and we'd go back to pretending we like JavaScript while writing in CoffeeScript. :)
- Animus7 15y agoWeb programming is certainly fragmented by divergent implementations, but the conclusion doesn't follow from the premises. Adding another language doesn't automatically add browser compatibility problems. Who knows what "structured web programming" is, as Google defines it? For all we know, Dart could be a unification framework that compiles to browser-independent JS/CSS/DOM. In which case, the Dart would be very good for reducing implementation fragmentation.