3 ms·
A UI framework has to accommodate a huge range of projects of massively varying complexity, from barebones text layout to global enterprise across hundreds of t
by pizza 8y ago
A UI framework has to accommodate a huge range of projects of massively varying complexity, from barebones text layout to global enterprise across hundreds of types of devices. But people also want it to be simple enough to learn easily, prototype quickly, and maintain long-term without significant headaches. There ain't no such thing as a free lunch when it comes to simplifying complexity, so one framework cannot rule them all. So we get new ways to do stuff, constantly.
- simion314 8y agoBrowser developers are for some reason putting effort in JS engines, speed but ignore working on the UI elements, you still can't CSS the scrollbars in Firefox (so projects use big JS libraries) , you can't css the select element and it's options so again you have to use JS to create a custom select, but some projects will use some jQuery library for this missing components, others will use bootstrap, others will wrap this other ones... web components could make this mess a bit cleaner but for some reason they are not ready or nobody uses them.