@jaffathecake PE is fundamentally about restricting applications to ones that CAN be written without JS.
@scottjehl Discourse has broad access, via <noscript> and a day of work. What are you arguing?
-
-
@wycats That's great. Noscript would cover browsers with JS off, but it doesn't help a failed JS request, slow networks, proxy browsers, etc -
@wycats might as well start with that markup unqualified by noscript if it's available and functional anyway is all I mean. -
@scottjehl Then you need to do the work to wire it up, which is non-trivial with JS-rendered HTML. It will come, just not yet. -
@wycats old discussion but I was curious if there’s been any progress on this issue? We’re evaluating options for upcoming work. Thanks! -
@scottjehl Which issue exactly? -
@wycats basically, we want to be able to consider Ember for its features, but need to be able to serve HTML for performance & browser compat -
@scottjehl@wycats Benchmarking MVC frameworks now, seeing very slow perf for even a trivial todo app on 3G, initial server render helps - 6 more replies
New conversation -
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.