4 ms·
Another important consumer-end feature of splitting style/structure is it allows clients to have custom styles, accessibility-oriented styles, by just swapping
by keerthiko 8y ago
Another important consumer-end feature of splitting style/structure is it allows clients to have custom styles, accessibility-oriented styles, by just swapping out the "styling" content of an application/page without needing to swap out or inject into the UI structure/code.
The benefits to developers are more "trade-offs", but I think it generally is a better raw framework to work in without significant IDE-assistance to do development.
- taeric 8y agoThis is an important feature that, statistically, nobody uses. Worse, I challenge you to try it on a major site. :( Again, I like the argument. I just feel there is more taking about it, than benefits from it. Empirically, it just falls flat.
- keerthiko 8y agoYou are probably right. But also statistically, "nobody" is disabled or needs accessibility features. That's a poor argument for running in the opposite direction from providing them. Benevolent systems cater to the least powerful user, not the median user, and I think it's good to support benevolent systems wherever possible, because businesses are naturally biased against benevolence.
- taeric 8y agoI challenge that. There are fewer disabled users, true. Statistically, they do exist. They far outnumber folks that use this feature.