Re: Progressive Enhancement - Why is JavaScript the magic line that must not be crossed and not new HTML5+/CSS3+ features? #dogma
-
-
@wycats@jaffathecake As@scottjehl said, PE means pick a baseline and enhance from there. Baseline could well require JS to begin with. -
@joemarini@jaffathecake@scottjehl so by your definition, a 100% JS app could be called "progressively enhanced"? -
@wycats@joemarini@jaffathecake this would not be my definition, but feel free to tag me out and carry on. :) -
@scottjehl@joemarini Just muddying the waters. My argument is that devs who focus on PE miss opportunities to do great things. -
@wycats Complex PE takes more effort than JS-only. Between users and developers, only devs have the choice to improve access. It's up to us. -
@scottjehl more work means fewer features. Also, requiring PE means some things can't be done at all before exhausting complexity budget. -
@wycats all fine reasons one may decide that the reach is not worth their time, but that's not a great precedent for others, or a framework. -
@scottjehl Discourse has broad access, via <noscript> and a day of work. What are you arguing? - 14 more replies
New conversation -
-
-
@wycats@jaffathecake it'd be helpful to see some examples of core content & features that you've found can not be delivered without JS.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.