5 ms·
> The situation is even worse now. Is it really? I have the exact opposite opinion. I mean, I feel like the industry has pretty well standardized on React in T
by hn_throwaway_99 4y ago
> The situation is even worse now.
Is it really? I have the exact opposite opinion. I mean, I feel like the industry has pretty well standardized on React in Typescript for the front-end on web apps. Sure, there are other technologies that do different things (e.g. Svelte, and someone else mentioned Phoenix LiveView), but for the standard "I'm building a CRUD-focused web app", there are simple choices to make and it's easy to "do the right thing". I contrast this with 2016, when things were still in flux so it was much easier to make what turned out, in hindsight, to be the "wrong" choice (e.g. Angular or Flow). Plus, tooling support is much better now.
- mattlondon 4y agoReact is used a lot, but it is certainly not the standard. Angular is still used extensively, especially in enterprise
- hn_throwaway_99 4y agoI'd still argue that React is very much the default for new applications where legacy interop or existing team familiarity isn't a factor. I mean, this is obviously an extreme example, but COBOL is also still used extensively in the enterprise, yes it's still not really used for any new projects.
- EugeneOZ 4y agoAnd you are still wrong. Bigger companies often pick Angular.
- mattlondon 4y agoI'd say you are still wrong. Anecdotal evidence: I have recently started on a new green field project in a large enterprise and it was Angular. React is just utter trash for organisations where maintainability is a concern.