5 ms·
I disagree with your ending note. I like React and have been using it professionally for over 2 years, but I wouldn’t recommend anyone to use something just bec
by rochak 7y ago
I disagree with your ending note. I like React and have been using it professionally for over 2 years, but I wouldn’t recommend anyone to use something just because it is an industry standard. At my work, for example, the upper management is now convinced that microservices are going to solve all of their current maintainability problems, while the fact is that there are a lot of employees that write shit code, who will also develop shit microservices.
- acdha 7y agoI might pick a nicer phrasing for your last point: if your team is not good at clean architecture (separation of concerns, conceptual model, etc.), microservices will “solve” that in the same way that adding gasoline solves a fire. If your team has gotten better at that, however, it might be a good strategy for migrating pieces out of an old system.
- s_y_n_t_a_x 7y agoMy sole reason is to point new developers to the skills that nets them the most job opportunities. Learn the most popular (and imo the best) framework first. People bitch about the web being too hard and too many choices. Then when you say to just use the most common stack, they bitch that you should choose X instead. Doesn't make any sense. React also has the largest ecosystem, is the most flexible, and the most feature complete. (I can natively target nearly all mobile/desktop environments)