CyberAP's profile picture. Sr. Frontend Engineer @gitlab (https://gitlab.com/slashmanov)

Stas Lashmanov

@CyberAP

Sr. Frontend Engineer @gitlab (https://gitlab.com/slashmanov)

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/git…


Thank you Ruby

CyberAP's tweet image. Thank you Ruby

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.

CyberAP's tweet image. 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?


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.

This post is unavailable.

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 -->.


Loading...

Something went wrong.


Something went wrong.