Well, I'll give you that having a single approach is simpler indeed, that also works against adoption from new developers who don't really like the paradigm or being forced to work with a single provider (such as Microsoft).
Personally, I like the varied approach JS gives you, and the mess with teams you mention I've never experienced it myself. It's always about setting standards from day one and then making sure everyone follows them. But that should be done with any technology, you can have JAVA as your main language, but still, there are different ways to write JAVA, so code standards apply. With JS it's the same thing.
I won't speak to your React use case since I don't know React nearly enough to have an opinion about it, but considering there's so much work being done with it, I would say it probably has its merits.
I personally hate JAVA because of how much you need to write with it. In fact, any self-respecting JAVA dev will probably not code JAVA without Eclipse or one of the main IDE, which I think speaks to how un-user friendly that language is, whether JS can be written with any editor without too much fuzz.
That being said, I'm not here to start a flame war about best or worst programming languages, rather I want to understand what are the pain points of JS developers in order to see if I can provide some help, so thanks again for sharing!
You mention needing other libraries to do different things, and that's really one of React's strengths. I think the problem comes from people thinking React is a framework. It's not, it's a view library. It has a lot of built in features, sure, but it's not meant to be an all in one solution. And that's great, because all in one solutions are often very heavy, and you're forced to carry the weight for parts you don't intend to use. React starts off incredibly lightweight, and if you need to add something to it, you can pick and choose the solution best suited for your application. You can do anything with react+other libraries as countless of companies have showed us. Needing to use other libraries to build complex applications isn't a con. And anyway, with enough experience you'd be surprised how complex of an app you can create with just plain react.
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.
Well, I'll give you that having a single approach is simpler indeed, that also works against adoption from new developers who don't really like the paradigm or being forced to work with a single provider (such as Microsoft).
Personally, I like the varied approach JS gives you, and the mess with teams you mention I've never experienced it myself. It's always about setting standards from day one and then making sure everyone follows them. But that should be done with any technology, you can have JAVA as your main language, but still, there are different ways to write JAVA, so code standards apply. With JS it's the same thing.
I won't speak to your React use case since I don't know React nearly enough to have an opinion about it, but considering there's so much work being done with it, I would say it probably has its merits.
I personally hate JAVA because of how much you need to write with it. In fact, any self-respecting JAVA dev will probably not code JAVA without Eclipse or one of the main IDE, which I think speaks to how un-user friendly that language is, whether JS can be written with any editor without too much fuzz.
That being said, I'm not here to start a flame war about best or worst programming languages, rather I want to understand what are the pain points of JS developers in order to see if I can provide some help, so thanks again for sharing!
You mention needing other libraries to do different things, and that's really one of React's strengths. I think the problem comes from people thinking React is a framework. It's not, it's a view library. It has a lot of built in features, sure, but it's not meant to be an all in one solution. And that's great, because all in one solutions are often very heavy, and you're forced to carry the weight for parts you don't intend to use. React starts off incredibly lightweight, and if you need to add something to it, you can pick and choose the solution best suited for your application. You can do anything with react+other libraries as countless of companies have showed us. Needing to use other libraries to build complex applications isn't a con. And anyway, with enough experience you'd be surprised how complex of an app you can create with just plain react.