I think addressing an issue with a more compassionate delivery would’ve been a bit better. Especially to the people outside of the React team, those who are also contributing to that open source and working hard to help deliver out of the kindness of their hearts
-
-
Replying to @TaelurAlexis
I hear you, and that's my usual tack...but the hour is late. A pervasively unusable web is leading to this being the last generation of web dev: https://player.vimeo.com/video/364402896 Despite years of begging, the React community and it's leaders center developers over users.
3 replies 0 retweets 3 likes -
Replying to @slightlylate @TaelurAlexis
Now Alex, you know this is not accurate, even in this thread we see that - Gatsby supports no-JS - NextJS will soon support no JS & better progressive loading of JS - The React core team are building Suspense to improve things further. Best to avoid absolute statements
1 reply 0 retweets 2 likes -
Replying to @chofter @TaelurAlexis
If what you're saying is "there is potential that this ship could turn", I agree! And I've agreed at every single moment from when I got so frustrated that I had to give a talk like this: https://www.youtube.com/watch?v=4bZvq3nodf4 … ...and still, failure rates of React sites have not decreased.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @TaelurAlexis
What do you say to the proposal that browser vendors do an inventory of the most common components in open source (pick, say, 10) and build them into the platform? Obviate the need for frameworks for 90% of use cases. Multi select, simple charts etc
1 reply 0 retweets 1 like -
Replying to @chofter @TaelurAlexis
I am a fan of extending the platform to integrate userland needs....but this has also been my biggest professional failure: I helped push classes, promisies, and other improvements over the line only to see developers (*cough* React *cough*) care more for OldIE than users
1 reply 0 retweets 0 likes -
Replying to @slightlylate @TaelurAlexis
Is anyone driving this? What end user facing component has been added in the last 10 years? Why do custom date pickers even exist?I just hand built yet another multi select component, & don’t get me started on dynamic lists again.... Can we aim for 5 new components a year?
3 replies 0 retweets 4 likes -
I need to write about this, I guess, because this keeps coming up but in short words: I think no. This assumes that the view from the outside about how long any of this takes is accurate - it isn't.
@gregwhitworth@stubbornella2 replies 0 retweets 0 likes -
Replying to @briankardell @chofter and
What specifically do you mean by "I think no?" Are you referring to a specific aspect of his question that you don't believe we're looking into?
1 reply 0 retweets 0 likes -
Replying to @gregwhitworth @chofter and
A lot of people have extrapolated math like "in 30 years we have ~130 elements/we haven't done new ones in several years, so 5 elements/year". But, the math doesn't really work like that. We absolutely can start queuing, but support for 5 new elements next year seems unlikely
2 replies 0 retweets 0 likes
That's just an investment and research question. We have a big defecit. We could do more than 1/yr for half a decade and only have caught up to demand.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.