4 ms·
As discussed extensively in this thread: >https://news.ycombinator.com/item?id=34796277 https://news.ycombinator.com/item?id=34796277 I would say what is bad
by Ambolia 4y ago
As discussed extensively in this thread:
>https://news.ycombinator.com/item?id=34796277 https://news.ycombinator.com/item?id=34796277
I would say what is bad is all GUI or application development over the web. React solves some problems of application development and introduces others. If you are really annoyed by the problems introduced by React and want a new platform that doesn't have those problems, that's fine, go for it. But be clear that the web is a broken environment for application development all the way down and there's no silver bullet. You will find problems in whichever stack you choose. Analyze clearly what trade-offs you are making and don't think that everything was fine until React arrived, React was created to address certain issues.
Those problems may have been partially addressed by new web-standards, but not all have been addressed, and those web-standards have not been battle-tested hard enough to decide if the solutions are good enough.
- Existenceblinks 4y agoIt's tough for engineers when React already loses in any technical challenge. If a business were selling cheap product, that would justify poor materials. But if your business is high-end, why don't use the best materials?