Post #1452521

Replies (1)

• @kawazoe@transfem.social 2026-04-20 16:20

  @WeirdWriter@caneandable.social @MoritzGlantz@mastodon.social A lot, and I do mean A LOT of UI work on web tech stacks is just historical overhead. 99% of the code is unnecessary when you target the latest version of Chrome only. 95% of the code is unnecessary if you target the latest version of Chrome, Firefox, and Safari only. It goes down to 90% if you add mobile versions. The issue is that modern UI frameworks have so much extra stuff that can justify their presence in your project. Imagine if it takes 100hrs to make a UI, but there is that one component that's incredibly difficult to do by hand that would take 90hrs to get right in your UI. If you can find a component library if that has that feature out of the box, it doesn't matter the rest of the site can be done in 10hrs without it. You'll have to use that framework for everything if you want stuff to feel cohesive, so you'll spend 15hrs to do the whole site with that framework, even if you end up with 10x more complexity and overhead, just so you can get that single component for free. Those libraries always use cohesiveness to buy you in. No one wants to have 5 different design languages and dev tools to learn and customize in their projects, so all of those frameworks just have to do everything, making them massive and slow moving. They gather bloat until a new one comes in... all of that because you can't just use the components they do great individually.

  Open ##1888834