The web has gone super-linear, tho. Our data shows we're getting worse faster than HW is improving. Also, in many segments, HW is not improving. Double-whammy, and JS bloat is the root cause.
-
-
Replying to @slightlylate @chriseppstein
I'd be curious for some analysis on what bits are growing, if you understand what I'm asking. Like, as in, what is it that is trying to be done that we could avoid here with better features and still meet expectations
2 replies 0 retweets 5 likes -
Replying to @briankardell @chriseppstein
The community is largely rejecting non-user-space answers. Many causes, but all lead to bad client-side experiences.
1 reply 1 retweet 6 likes -
Replying to @slightlylate @chriseppstein
Sorry, can you clarify? Really don't know what you mean there
1 reply 0 retweets 3 likes -
Rephrased: what's an example of a thing lots of people are using that is a significant chunk and has a native answer that isn't getting used? Is that what you mean?
1 reply 0 retweets 5 likes -
Really i would like to better understand what you're saying ^^^
1 reply 0 retweets 0 likes -
Replying to @briankardell @chriseppstein
Ah, sorry for the late reply. One small example: I can't tell you how many copies of Promise (and Promise-alike) polyfills I see in apps I dissect.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @chriseppstein
Ah yes.. Tag should discuss this as there was some disagreement iirc... Will find you a pointer tomorrow to what i mean
1 reply 0 retweets 0 likes -
Replying to @briankardell @chriseppstein
Other examples abound, but in general the view amongst the frontend community is that JS is cheap (it's not) or that hardware is getting faster (in growth markets, it's not).
2 replies 0 retweets 3 likes -
The promise situation could be improved through more hookability and also by waiting. I don't see promise polyfills sticking around in new apps for much longer. Last week's Ember "reader question" was about this:https://discuss.emberjs.com/t/readers-questions-why-does-ember-still-use-rsvp/14736 …
1 reply 0 retweets 1 like
TLDR we're working on it and are close to removing it. Totally agree that the web doesn't need promise polyfills anymore.
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.