JSX: yesTypeScript: sureCommonJS & ESM: no problemDecorators: yeehawWeb Components: how dare you, this is too much complexity
-
Zach Leatherman :11ty:replied to Naiyer last edited by
@naiyer whew, Iāve definitely felt that Vue 2/3 pain
-
@naiyer what about Web Components v0 -> v1? But yeah Web Components are stable now so that's good!
-
Zach Leatherman :11ty:replied to Tegan last edited by
@rawrmonstar @naiyer v0 was Chrome-only. We can have a conversation about overly aggressive single vendor web features but this isnāt one of those
-
Teganreplied to Zach Leatherman :11ty: last edited by
-
-
Zach Leatherman :11ty:replied to Tegan last edited by
@rawrmonstar @naiyer for sureāI donāt think the v0 thing was good either. But folks blaze past the two+ impls best practice all the time (which is risky!). e.g. Astro shipped View Transitions stuff when it was Chrome-only and no one batted an eye (wellā¦Ā I did, but āļø)
-
Teganreplied to Zach Leatherman :11ty: last edited by
-
Zach Leatherman :11ty:replied to Tegan last edited by
@rawrmonstar @naiyer you get what I mean thoughāmultiple impls is an important milestone
-
Mike Aparicioreplied to Zach Leatherman :11ty: last edited by
@zachleat CSS: what do I look like a fucking rocket scientist? WTF even is this shit?
-
Zach Leatherman :11ty:replied to Mike Aparicio last edited by
@peruvianidol š«£š«£š«£ I still have trouble wrapping my head around a preference for HTML over CSS, it just doesnāt fit the stereotype