Re: Progressive Enhancement - Why is JavaScript the magic line that must not be crossed and not new HTML5+/CSS3+ features? #dogma
-
-
Replying to @jaffathecake
@jaffathecake PE is fundamentally about restricting applications to ones that CAN be written without JS.2 replies 0 retweets 3 likes -
Replying to @wycats
@wycats@jaffathecake "PE is about restricting applications to ones that CAN be written without JS." No, I'm sorry that is COMPLETELY wrong.1 reply 0 retweets 1 like -
Replying to @joemarini
@joemarini@jaffathecake really? Please, enlighten me.2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@jaffathecake As@scottjehl said, PE means pick a baseline and enhance from there. Baseline could well require JS to begin with.3 replies 0 retweets 0 likes -
Replying to @joemarini
@joemarini@wycats@jaffathecake@scottjehl -@tomdale is right a lot of this is semantics - we need a new term to discuss effectively imo3 replies 0 retweets 0 likes -
Replying to @briankardell
@briankardell@joemarini@wycats@scottjehl@tomdale to be fair, all these wrapper terms we use are fuzzy, especially "web app"2 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake "web app" means at least: uses HTML semantics to define content, URLs for navigation1 reply 0 retweets 0 likes
@jaffathecake a "web site" is one way to build it. Another is HTML templates, a JS router and JS management of model+template=DOM
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.