I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
As much as reasonably possible. The better you understand JavaScript itself (and the Web API's), the easier it will be to learn to use React, or Svelte, or whatever other framework you choose.
On top of that though, having a solid understanding of how to do things in JavaScript without needing to use a front-end framework makes you a much better JavaScript developer. It means you'll be more likely to understand any arbitrary JavaScript code you come across, it makes it easier to work around issues you might have with whatever front-end framework you sant to use, and it means you'll have an easier time understanding how the framework actually works (which in turn helps you avoid bugs).
That said, unless you have some reason to learn React specifically, I'd encourage you to look instead at Web Components. They have far less overhead than a conventional front-end framework, are usually more portable, and still provide the main thing most people want a front-end framework for (reusable UI components.
Thanks a lot, I do have a reason to learn React but I'll definitely get familiar with Web Components first, maybe that'll give a more general insight on the concept than getting straight to the framework.
I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
Indeed, and even I don't feel that they're a silver bullet. I do, however, feel that they don't get mentioned anywhere near enough, hence my making a point to mention them here (and I think they're a better introduction to the concept of the shadow DOM than most of the UI frameworks that make use of it are, since you actually have to use it yourself with Web Components, you end up with a better understanding).
As far as 'who was right', I suspect the answer will end up being somewhere in-between. Web Components definately have their issues, but so does every UI framework out there.
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.
As much as reasonably possible. The better you understand JavaScript itself (and the Web API's), the easier it will be to learn to use React, or Svelte, or whatever other framework you choose.
On top of that though, having a solid understanding of how to do things in JavaScript without needing to use a front-end framework makes you a much better JavaScript developer. It means you'll be more likely to understand any arbitrary JavaScript code you come across, it makes it easier to work around issues you might have with whatever front-end framework you sant to use, and it means you'll have an easier time understanding how the framework actually works (which in turn helps you avoid bugs).
That said, unless you have some reason to learn React specifically, I'd encourage you to look instead at Web Components. They have far less overhead than a conventional front-end framework, are usually more portable, and still provide the main thing most people want a front-end framework for (reusable UI components.
Thanks a lot, I do have a reason to learn React but I'll definitely get familiar with Web Components first, maybe that'll give a more general insight on the concept than getting straight to the framework.
For fullness of picture, not every web developer shares idea of web components, for example dev.to/richharris/why-i-don-t-use-....
Time will show who was right.
Indeed, and even I don't feel that they're a silver bullet. I do, however, feel that they don't get mentioned anywhere near enough, hence my making a point to mention them here (and I think they're a better introduction to the concept of the shadow DOM than most of the UI frameworks that make use of it are, since you actually have to use it yourself with Web Components, you end up with a better understanding).
As far as 'who was right', I suspect the answer will end up being somewhere in-between. Web Components definately have their issues, but so does every UI framework out there.