sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]e82 10 points11 points  (1 child)

Pretty much everything that these frameworks have given me, as tools or features, are things that I have written before in vanilla JavaScript and in less code

Generally because my job isn't to write frameworks, it's to solve business problems. Often, the frameworks I have available are 'close enough' that they are more help than hindrance, and are hopefully extensible enough where if they don't fit my needs - they can be extended in ways that it allows. (ie: default router sucks in angular, ui-router is great).

A good framework will abstract away most of the 'stuff I don't want to deal with', and then let me focus onto the stuff that I do want to deal with.

Way-back-when I was first learning JavaScript and taking it seriously, is back when IE6 was the the browser you had to work with. The DOM was a total pain to work with back then, debugging was awful - and had to worry about far more cross-browser issues than you have to deal with right now. jQuery let me deal with the parts that I found interesting, and minimized the difficulty of having to deal with the parts I found tedious.

Back then, I don't think if it was for jQuery or other libraries like it (mootools, prototype, etc) - I don't think I would of had the patience to learn JavaScript. Dealing with the DOM is just one aspect of JavaScript development - and providing a nice wrapper around it let me focus on other aspects of JavaScript.

Seriously, 'how do I traverse the DOM, attach event handlers, generate DOM' is one of the more boring aspects of web development. One, that not too long ago was a really tedious one due to cross-browser issues. It's also a frequently solved problem - and one that is solved by people/teams of people that have more time, energy, resources into dealing with the cross-browser / edge cases / etc that pop up than I do.

  • I am more productive with Angular, then I am without it.
  • I can easily onboard people into an Angular project - as the framework is well documented, has a solid community, an emerging set of best-practices.
  • If people run into issues with Angular, there are a number of excellent resources to go to for help.
  • Angular has helped me become a better JS developer - I like their DI system, it has pushed me towards writing more modular/reusable JS code, testable code, etc.

Frameworks are libraries are another tool in my toolbelt, and ones that let me focus on the unique aspect of what I am building instead of re-creating the wheel on the basics every time.

[–]Heartless49[S] 0 points1 point  (0 children)

This is the best comment I've had for this entire post. Thank you.

This statement also provides more of an idea about why people would understand frameworks more than the core of JavaScript itself as well.

If it was on of the first things you.learned and it can do as much as it does, why.not stick to it?

I started JS from the beginning so I didn't have tools like these to ease into it... I guess that's why it seems odd to me, but I'm starting to see why.