Comment by Ryosuke on "What's the advantage of using any front-end framework like 'Angular' or 'React' over VanillaJS?"

Why use any framework, library, or plugin? It makes your job easier. It does things you need that you don't want to build it yourself.

I could just do an long xhr request in Vanilla JS, or I could use a single line $.get() in jQuery and call it a day.
I could create my own templating system, or I could lean on things like Handlebars or even Vue components.
And don't get me started on frameworks like A-Frame that make VR child's play for any developer, rather than forcing them to delve deep into WebGL.

At the end of the day, it's not impossible to complete projects without React, but it makes certain tasks easier or more efficient -- like state and DOM management.

I recently started dabbling in video game design on the web using Javascript, and I ended up using a framework called Phaser to make the game. I could have just coded everything I needed myself, like tilemap/sprite interpretation, collision detecting, or complex physics. But I realized by the time I finished coding the necessary classes, I'd have wasted weeks I could've spent coding the game using a pre-existing framework.

I wanted to be a game designer, not guy who designs game frameworks.

I could just do an long xhr request in Vanilla JS, or I could use a single line $.get() in jQuery and call it a day.

Or you could call a Vanilla JS fetch() and call it a day, or library like axios or Api. It is really sad that you need to include whole, huge jQuery just to do fetch.

I could create my own templating system, or I could lean on things like Handlebars or even Vue components.

Or you could contribute to this specific Web Standards proposal, but overall, yes, Handlebars/Vue is simple and does the job, however this proposal's some implementations already will give you same result faster for much less resources. The question was about "framework like Angular/React", not about rambda, handlebars.

And don't get me started on frameworks like A-Frame that make VR child's play for any developer, rather than forcing them to delve deep into WebGL.

JavaScript and Web APIs were made for a typical scenario, not game development. This question, again, was asked from a "frameworks like Angular/React" perspective which are for this typical scenario and DOM manipulation, not canvas or WebGL or WebAssembly.

At the end of the day, it's not impossible to complete projects without React, but it makes certain tasks easier or more efficient -- like state and DOM management.

No, it doesn't make DOM/state management easier and more efficient. What is YOUR personal, honest life experience or do you just follow the hype, fake news and articles without doing any research? DOM is NOT slow and you DON'T need any new jargon like "state management" to deal with data, stop believing all that marketing bs online. Can you give me a real use case example and I will give you a simple JS code which will solve the problem, but I guess, you like everyone else for last years when I asked same question will just chicken out from this conversation without defending their holy garbage called React.

@oscarthegrouch My question was specific to frameworks like 'Angular', 'React' and 'Vue'. Using JQuery and other libraries certainly help in making code shorter. I'm currently learning Angular and building a small application that involves only three components. It took me a whole lot of time and code to make them communicate with each other. I could be wrong but I don't see any advantage in using them.

Few people have mentioned that they enable you to onboard new developers a lot easier. But aren't these things secondary? Are these frameworks making my application's performance better in any way?

I'm still a novice and there's certainly a lot left to learn but so far the only thing I've experienced is that in the name of modularity they're just making small tasks more complicated.

kartik chauhan I think much of this is because you're new at using these frameworks. Of course there is an initial learning curve which will appear to be slowing you down, but someone who has been using Angular for years can slap something together much quicker.

I don't think any frameworks are known for their performance... If you want to get into that then you develop using C, C++, maybe Rust, or even some modules in assembly language.

I wouldn't even say that frameworks are known for security either but you have to keep in mind that they may actually improve performance and security when you have a bunch of novice developers who would otherwise overlook aspects that the framework has taken care of for them. Again, is this the best process for the developers' individual education? probably not. But it all comes down to the requirements and resources of the project.

Search Hashnode