Post #2392984
2026-03-19 10:19 UTC
@leaverou@front-end.social @TC39@fosstodon.org But we want CSS as CSS and HTML as HTML, the way we get JSON as JSON, not at strings or bytes. Won’t we have to “ad hoc” type them down the road anyway making it just delayed further but not continuing to work towards them now?
Replies (1)
-
@leaverou@front-end.social 2026-03-20 20:40
@westbrook@mastodon.social When designing any product/API/language a common tension is: 1. Cover all use cases at 80% (low-level primitive) vs 2. Cover only the common cases at 100% (high-level primitive). The right call depends on the specifics, including: 1. What % of use cases would 2 leave out? 2. How painful are those use cases now? If the answers are "high" and "very", 1 tends to be the right call, and buys you time to do 2 well, because now it's about reducing friction, not making things *possible*.