Staff Frontend Engineer @gitlab (https://teapawt.net/t.co/q8MMrM0IEz)
Joined March 2009
- Tweets8K
- Following60
- Followers323
- Likes2.7K
There's a lot of opportunity for truly modular frontend frameworks out there. No popular framework offers you to extend their compiler or runtime. Instead of hacking the framework into doing what you really want wouldn't it be cool to be able to write a proper feature yourself?
Today @GitLab has become the largest (at least to my knowledge) open source repo with a @vite_js support.
This was a year long journey and we're not 100% sold on migrating from Webpack (mostly due to waterfall effect) but still great first impressions!
gitlab.com/gitlab-org/gitlab…
I've discovered that out-of-order streaming ’just works’ with Declarative Shadow DOM (kindly pointed out by @Keithamus). Could save you quite some bytes on the implementation!
stackblitz.com/edit/node-5sb…
Oh wow, it even properly handles streamed element removal and skips everything till the closing tag. Looks very much reliable.
stackblitz.com/edit/node-bmf…
The fact that content-intrinsic-size doesn't allow for just 'auto' values makes content-visibility so much harder to use (if we ignore all the major bugs it has in Chromium). It could've become such a great alternative to virtual scrolling (and would've won in most of the cases).
That's what you get for using client-side validation (hello @stripe). My trying to add a new debit card to @1Password. No way to submit a fully filled in form with zero errors. I bet it is also non-trackable error.
Why do we still call it Single Page Application when it is a Single Document Fetch, not a Single Page?
The State of CSS'22 results are...worrying. We've recently got full browsers support for Cascade Layers. There are big issues with Content Visibility in Chrome. And layout perf debug is nonexistent there. But all people want are nesting and Tailwind. Oh, there's also CSS-in-JS!😐
I hope this is not something that will be a 'hot new thing'. We've been through this with Rails. Interactivity over the wire is a bad UX because it relies on something you don't control (Internet infrastructure). Performance problems should & can be solved in a user-friendly way.
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
Streaming and SSR-first approach must change the way we think of serving CSS. It doesn't make sense to serve small chunks of HTML if incremental rendering is still blocked by a CSS for the whole page. My guess is that <style> should become the first tag of the component's output.
Crazy idea, but why no one (I heard of) uses HTML comments as a medium to transfer state from server to client?
Comments are super cheap to parse and shouldn't be as heavy as plain text or data attributes. The only sequence you have to escape is -->.
I just gave a talk @gitlab about Streaming. Come see the recording if you're curious about client side rendering performance, SSR and how Streaming is related to all of that.
youtube.com/watch?v=4zbJQCSR…
Also here's the Worker demo I've shown in the presentation: slashmanov.gitlab.io/vue-wor…
Try it for yourself!
This is so frustrating to see a common pattern of misapplying technologies that can do only one thing great.
Example: Instagram uses virtual scrolling for infinite image feed and it works mostly great.
UX and accessibility should never be a price for great performance.
’Anyone can build a bridge that stands, but it takes an engineer to build a bridge that barely stands.’
It's the same story here. Achieve great performance and preserve UX at the same level or improve it.