It's not that Vue isn't applicable for data-heavy applications. It's just not (usually) worth the effort to adapt Vue when there's React. At the end of the day it's about what gets the job done in the most efficient way and how to monetize customer's pocket. :)
It's just not (usually) worth the effort to adapt Vue when there's React.
This sentence makes literally zero sense.
Remind you that I'm talking about enterprise here
"enterprise" you're talking about means nothing and says nothing about the quality of the tool. Enterprise merely means "they probably have more money to burn than agencies".
In real world scenario, you'd expect frameworks not to alter the way you use underlying language. Vue excels here, since it's good old JavaScript (or TypeScript) without any surprises. It's template syntax resembles HTML more than anything else. The 90% of the learning curve is done by this.
Choosing accurate tooling DOES matter and SHOULD matter. Sane choice is choosing a tool that doesn't require years of adapting to the tool. React is not like that. It's also made by the largest spyware company on the planet. There's plenty of moral reasons why not to go with React, but they also make it easy to avoid it because of technical reasons.
I consulted on plenty of enterprise projects. React ones were always the ones that went through the hands of multiple "teams", they were never finished and it was spaghetti code with a ton of libraries thrown together, mixed in a nice soup of "where the hell does this thing even start executing" React noodles.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's not that Vue isn't applicable for data-heavy applications. It's just not (usually) worth the effort to adapt Vue when there's React. At the end of the day it's about what gets the job done in the most efficient way and how to monetize customer's pocket. :)
So it’s not the matter of framework then - but how good your hands are and grow from the right place lol
As I said - that's how it is when it comes to non-enterprise applications. Doesn't matter at all. Go with what feels right. :)
Remind you that I'm talking about enterprise here. It's the only area in which choosing the right library/language/framework matters.
This sentence makes literally zero sense.
"enterprise" you're talking about means nothing and says nothing about the quality of the tool. Enterprise merely means "they probably have more money to burn than agencies".
In real world scenario, you'd expect frameworks not to alter the way you use underlying language. Vue excels here, since it's good old JavaScript (or TypeScript) without any surprises. It's template syntax resembles HTML more than anything else. The 90% of the learning curve is done by this.
Choosing accurate tooling DOES matter and SHOULD matter. Sane choice is choosing a tool that doesn't require years of adapting to the tool. React is not like that. It's also made by the largest spyware company on the planet. There's plenty of moral reasons why not to go with React, but they also make it easy to avoid it because of technical reasons.
I consulted on plenty of enterprise projects. React ones were always the ones that went through the hands of multiple "teams", they were never finished and it was spaghetti code with a ton of libraries thrown together, mixed in a nice soup of "where the hell does this thing even start executing" React noodles.