Post #2392990
2026-03-20 20:40 UTC
@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*.
Replies (1)
-
@leaverou@front-end.social 2026-03-20 20:47
@westbrook@mastodon.social Of course, here CSS modules have already shipped in 2/3 so it's low-hanging fruit to support them. I'm not suggesting doing Import Text *instead*, unless we figure out time travel meanwhile. But we should definitely focus on these primitives before asking for any other types IMO or this situation will keep repeating.