3 ms·

This site screams at me don’t reinvent the wheel. The premise is that frameworks aren’t enough and developers are wasting time working too hard on things they a

This site screams at me don’t reinvent the wheel. The premise is that frameworks aren’t enough and developers are wasting time working too hard on things they already know. When I hear things like this it begs the question: Exactly how easy do you need it to be? Should UI developers not be required any greater effort than copy/paste? The reality is that most of the components the site proposes are already copy paste if you aren’t locked into a giant framework like React. Like some other comments have said there already is a common platform for building reusable UI components: web standards. The world surely doesn’t need a framework for riding on top of your framework.

Zarel 7y ago
As far as I can tell, this is a collaboration between Microsoft Edge and the W3C for deciding what reusable UI components should be put in web standards, and what they should be named. So it's already exactly what you want. What are you complaining about?
- austincheney 7y ago
  It’s an unnecessary artificial solution to a non-problem. If you need a reusable drop down you are fortunate because it already exists with full accessibility: the HTML select element. But but but it looks boring... CSS. But but but form elements are impossible to style and modify their behavior... probably because you are breaking accessibility for vanity. My complaint is that this idea is an unnecessary work around to sole something that isn’t a real problem to supplement your unnecessary work around (your giant framework). I have reinvented this wheel enough to know that people frequently want nonstandard things for nonstandard reasons because vanity is more important than everything else, accessibility is an add on to worry about later, and they are hopeless without the world’s largest framework to do their jobs for them. I already have to be saddened with framework nonsense spaghetti code by incompetent developers at work. The idea of taking mental laziness and bad ideas to another level for some senior surrogate dev to parent is horrific.

Zarel 7y ago

As far as I can tell, this is a collaboration between Microsoft Edge and the W3C for deciding what reusable UI components should be put in web standards, and what they should be named. So it's already exactly what you want. What are you complaining about?

austincheney 7y ago
It’s an unnecessary artificial solution to a non-problem. If you need a reusable drop down you are fortunate because it already exists with full accessibility: the HTML select element. But but but it looks boring... CSS. But but but form elements are impossible to style and modify their behavior... probably because you are breaking accessibility for vanity. My complaint is that this idea is an unnecessary work around to sole something that isn’t a real problem to supplement your unnecessary work around (your giant framework). I have reinvented this wheel enough to know that people frequently want nonstandard things for nonstandard reasons because vanity is more important than everything else, accessibility is an add on to worry about later, and they are hopeless without the world’s largest framework to do their jobs for them. I already have to be saddened with framework nonsense spaghetti code by incompetent developers at work. The idea of taking mental laziness and bad ideas to another level for some senior surrogate dev to parent is horrific.