2 ms·
Probably there will be a grass roots if devs hacking at home with not-Reacts, loving it, bringing it to work. It is not like you need to only use one framework
by quickthrower2 4y ago
Probably there will be a grass roots if devs hacking at home with not-Reacts, loving it, bringing it to work.
It is not like you need to only use one framework per company. There is a lot of melting-pot coding happening out there.
React was probably successful in part because it didn’t require a rewrite.
- shadowgovt 4y agoDepending on the scale and goals, there are huge advantages to companies standardizing on one framework. Nothing burns more than having to dedicate an additional quarter to a project because half the code you need to finish the task is sitting atop another API or, much worse, in a different language. And when we're talking web apps, There's real material cost to the end user in using more frameworks than are strictly necessary. React is large, but it tends to be large with a spanning set of features that means you don't have to glom something else in alongside it.
- quickthrower2 4y agoI agree that it is advantageous for companies to standardize but often they don't. React + Vue in one app might be a bit crazy but React in the main app and Vue in an internal app, or some secondary app might be OK. Resume-driven development is a thing, as well as joy-driven development. Devs are gonna be devs! There is a mild conflict between what is good for a devs career and what will make the shareholders of that company the most money. It is almost like a super-polite tug of war over future potential dollars between the two. Mostly incentives align but sometimes not.