Jump to menu

Vote down?

  1. Scott McMillin

    Comments like: “CSS transitions affect how elements behave, not how they are styled” are semantically loaded, because it would be easy to debate the meaning of behavior and styling with regards to client-side web development. Why not presentation and functionality? A case could be made that animations like a progress indicator fit squarely within the presentation realm and should not require the use of a JS library nor tests. The removal of said bit of presentation, while impacting user experience, would not (and should not) impact functionality. My point is that it’s not as cut and dried as it may appear.

    I think we’re going to see a transition from Web development to full-fledged application development for mobile and tablet devices in the coming years. And because of the limitations inherent in the Web ecosystem (browsers, standards, etc) decisions must be made about how certain features are implemented. Choices are very limited.

    The innovation that’s happening at Apple, Google, and Mozilla should and must move forward. For those of you who think certain features should implemented in Javascript, do some googling on the storied history of ECMAScript 4 and have a look at Crockford’s latest talk on the state of Javascript. Then imagine the future of web application development and place yourself in the shoes of an engineer at one of the aforementioned companies. Given all the restrictions, how would you achieve the goals of replacing iPhone native apps with web-tech versions? How would implement a web-based operating system?