Twitter | Search | |
This is the legacy version of twitter.com. We will be shutting it down on 15 December 2020. Please switch to a supported browser or device. You can see a list of supported browsers in our Help Center.
shubhie
Software Engineer , Web Platform. Tech lead. Manager. Collaborator in the open source powered web ecosystem. Past: , google JS infrastructure
437
Tweets
443
Following
4,305
Followers
Tweets
shubhie Nov 22
What's the regression? This is perhaps similar to issue of switching from MPA to SPA? UX is generally better (unless initial load really regressed) but loss of sample count makes it look like metrics regression
Reply Retweet Like
shubhie Nov 22
In a meeting I said "this data is not meaningful" for assessing / comparing perf of frameworks. Then realized that is precisely the point: the UI framework choice has little to do with perf outcomes. We need to hold wrapper frameworks like Nextjs, Nuxt etc more accountable though
Reply Retweet Like
shubhie retweeted
Rick Byers Nov 20
I'm proud of the team, and in particular, for putting in the hard work to analyze cross-browser behavior, drive spec discussions and work to add web platform tests. Finally this is going to be part of the web platform properly 🙂.
Reply Retweet Like
shubhie Nov 21
Replying to @mlrawlings
Marko looks great! Thanks! Yeah frameworks need to evolve towards progressive delivery, also need to cover much more though eg. data system, bundlers batching chunks smartly, servers and hosting supporting multi flush (eg AWS lambda lagging), "wrapper" framework easing DX etc
Reply Retweet Like
shubhie Nov 20
Loading performance is complicated, and often misunderstood. I gave a Blinkon talk on this topic based on my findings while working closely with a lot of production sites, powered by popular open source tech stack. Video: Slides:
Reply Retweet Like
shubhie retweeted
Rick Byers Nov 19
BlinkOn, the chromium web platform contributors conference, just wrapped up. All the videos are, amazingly, already posted here: . Thank you organizers, presenters and everyone who engaged in the conversation!
Reply Retweet Like
shubhie Nov 19
thanks, definitely striving for ripple effects and already seeing some early wins:
Reply Retweet Like
shubhie Nov 15
Yes that is actually easy to share, thanks for the suggestion!
Reply Retweet Like
shubhie Nov 15
Yes my team follows the RFC process and want to go even further with transparency. We thought about public newsletter or monthly summary etc Ideas are very welcome.
Reply Retweet Like
shubhie Nov 14
Replying to @MrAhmadAwais
Glad to hear it! Feel free to DM me on what specifically is helpful or we should do more of etc
Reply Retweet Like
shubhie Nov 14
Replying to @MrAhmadAwais
👋 you too
Reply Retweet Like
shubhie Nov 14
Believe it or not, Yes for my group.
Reply Retweet Like
shubhie Nov 14
One reason why Google dared to put a few engineers in this area (given extreme resource constraints) is due to the power of open source and network effects of good patterns propagating and copying across frameworks. I'm open to feedback on whether we are thinking of this wrong..
Reply Retweet Like
shubhie Nov 14
Replying to @threepointone
Thanks Sunil! I appreciate the opportunity to share broader context and provide more transparency.
Reply Retweet Like
shubhie Nov 14
Replying to @shubhie
It’s definitely a good time to step back and think about the larger picture. What can we do better. I’m very open to the community's feedback. DMs are welcome!
Reply Retweet Like
shubhie Nov 14
Replying to @shubhie
Very recently this work graduated out of incubation into a real longer term initiative. This wouldn’t have been possible without all your support and also our ability to show successes in Next.js. 8/N
Reply Retweet Like
shubhie Nov 14
Replying to @shubhie
5. A huge behind-the-scenes effort that is most challenging is bringing Chrome & web platform in alignment with the web developer audience & tech stack. Currently these are evolving often divergingly. This means working closely with web platform, standards, v8, devtools etc. 7/N
Reply Retweet Like
shubhie Nov 14
Replying to @shubhie
4. The next big thing is ensuring that successful patterns are implemented in more stacks and readily available to more developers. We need to do more here beyond documentation and facilitating copying. Next we are looking at Vue & Nuxt to expand our framework engagement. 6/N
Reply Retweet Like
shubhie Nov 14
Replying to @shubhie
Validation is against production sites using metrics, so real websites are our primary partners. We’ve also had a successful collaboration with the Angular team, they helped validate that our ideas are not over-fitted, they picked some of them. 5/N
Reply Retweet Like
shubhie Nov 14
Replying to @shubhie
3. A “wrapper framework” (like Nextjs, Nuxt) provides access to the dev workflow and spans the stack. So this is the place to validate ideas, bake in the successful patterns, and bury failed attempts. 4/N
Reply Retweet Like