4 ms·
I'll admit react is not the ideal technology for frontend but it is also not a bad one especially given the alternatives of designing one's own ui library. It
by aszen 5y ago
I'll admit react is not the ideal technology for frontend but it is also not a bad one especially given the alternatives of designing one's own ui library.
It is in demand not because it's the best technology but because it's well funded, has extensive library support and there's a wealth of tutorials online to learn it. Best technologies often don't win the popularity race.
React is still a very powerful way to create reusable uis but you need to be familiar with its internals and state management.
I personally would prefer writing my uis in something like elm which is far better designed and has some great ideas but in most projects I have to stick with react because everyone knows it.
- noduerme 5y agoI think I'm just disheartened that so many people would absorb a "just ok" technology because everyone else is, and then make it a basic attribute of their infrastructure. A few years ago I saw the same thing for Angular but not to the same extent. It just feels like a herd mentality. People say "oh, it's so much technical debt to rely on a custom UI platform". Really? Compared to something everyone uses, like, uh, JQuery? D3? Angular? Flex? I don't see how rolling your own incurs more technical debt than relying on a framework that may or may not have an ecosystem in a few years... and isn't the best solution anyway.
- aszen 5y agoI think you need to understand that most Dev's really cannot make a custom ui platform that will be easy to use and maintainable for the whole team. An advantage of open source libraries is that you can find people who are already proficient in the code while as for in house libraries you need to train them. Going in house is perfectly reasonable if it brings a substantial competitive advantage to the business otherwise it's a liability