just noting that popular devices aren't always developers' favorites, but still common
-
-
our blog has a bunch of wpt-driven research on PE, critical path, font, js start-render costs that I'd love for you to check out.
-
anyway. I follow & respect your work and didn't say you're on any 'other' side. Just respectfully disagreed with your point is all
-
btw I didn't mean to start an "us vs. them" argument here and really sorry if it came off that way.
-
I also respect your work and think people on the "JS" side dismiss the evidence-drive work of PE advocates too quickly as well
-
but the needling by PE advocates against any use of JS (example http://sighjavascript.tumblr.com/ ) creates an unnecessary rift.
-
I've had great convos w/ you and
@t, but somehow those nuances don't make their way into the way PE advocates talk in public. -
yep! But this whole thread back to
@slightlylate's first has been pretty great and amicable, to me. Good perspectives -
agreed. I think we all need to get together and discuss what enabling access looks like in 2020, and drive there
End of conversation
New conversation -
-
-
Instead, JS is considered "the bad parts" by PE advocates. Huge problem imo.
-
JS enables a much better experience for the developing world than JS-less PE.
-
fast boot is great too, though I haven’t seen enough live examples to say much more
-
static site AND JS-frameworked is arguably worst case scenario 4 user bandwidth
-
: false. Worst case scenario is > 10mb native app ;-) /cc
@scottjehl@wycats@briankardell@dalmaer@sil -
…that randomly redirects you to web app content in a webview!
@scottjehl@wycats@briankardell@dalmaer@sil - End of conversation
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.