In a rush? Skip to:
Rewind to 2013. ⏪
Our small dev team is about to ship one of its most impressive client projects to date. I'm at my stand-up desk, skimming through morning emails. My partner bursts through the office door:
"Something's wrong with our Angular app, man. I've got a
digest is already in progress error popping everywhere— can't figure out what's happening," he says, visibly nervous.
And I know all of this thanks to a robot.
Rewind to 2011. ⏪
But my friends and I had to build a soft real-time, task-oriented robot for one of our classes.
Peers told me to find a decent library for my use cases and pull off some copy/pasting art to get the socket communication job done. I could've done just that.
But I didn't. Although I didn't know it at the time, that was one of the best early career decisions I made.
In between managing my teammates' impatience and creating a not-so-clean, functional robot codebase, I learned a whole dmn lot*.
Let me quote an answer from koenpeters on Stack Overflow:
The Vanilla JS "framework" joke
Online forums are filled with questions like:
While Eric didn't coin the term per se, his site definitely helped popularize it.
A word on JS frameworks: pros and cons
First, what do I mean by JS "frameworks" here?
Yes, I know some are quite different, and some are not really frameworks. But please, for the sake of this article, let's declare them equivalent in their primary purpose.
→ They help you out by abstracting hard & complex code.
→ They help you ship code faster and increase development velocity.
→ They force you to focus on your app's value rather than its implementation.
I believe the greatest value there is to find in JS frameworks is collaboration. Their consistent interface and methods allow developers from, say, Canada, the US, and Brazil to understand one another and work together.
If you're building an app with [insert your favorite framework], when the time comes, you'll be able to find an experienced developer to hop into the project codebase with confidence. This person will be able to start tackling features without you needing to explain every part of your software architecture.
Another key reason to use frameworks is practice. They make you practice over and over again. And that's good! Practice always leads to mastery, whatever you're trying to accomplish.
Cons: Why I believe JS frameworks are not THAT awesome
People who work on framework implementation are all talented—at least most of them. They do a tremendous job of simplifying complex endeavors. But all of these levels of abstraction can quickly become evil.
Sure, frameworks are useful for small teams working on a single app. Yes, they'll save you some time (unless you're a refactoring addict). But what if you have more than one team working on more than one app? Do you think all team leaders will agree on a single framework for the whole suite of apps? And what if a new "cool kid" framework comes around in the future?
The problem is: the moment you settle on a framework, you impact every single upcoming engineering decision. Plus, you chain your team to a technology that will probably soon be deprecated. This stuff blows my mind.
Just think about what "jQuery developers" had to do: trying to catch up on Angular. Now, they're trying to catch up on React/Vue. Who knows what it will be tomorrow? And the sad, depressing loop goes on.
For me, it brought a lot of positive stuff:
- It helped me deliver a killer set of client features in a super short timeframe for an Ember app, without knowing jacksh*t about Ember.
- It got me a job offer from one tech giant because of a very simple library I wrote in my spare time.
- It made me identify bugs in libs implementation and suggest simple solutions super quickly.
Always be curious, always read the source material, and always try it yourself.
And some more specific advice:
- Whenever a new JS lib or framework is trending on Echo JS, Hacker News, or GitHub, go on and read the sources.
- Go on Stack Overflow and challenge yourself to answer vanilla JS questions on your own.
For beginners: I believe the learning flow outlined in this post by J.S. is a good starting place:
- Learn some basics on Udacity, Codecademy, freeCodeCamp or Udemy (either their free or paid courses)
- Read the YDKJS series!
Now for the learning resources:
I worked with my friend Franck, CEO at Snipcart to compile a carefully curated list of vanilla JS tutorials, books, courses, documentation, news sources, and blogs.
🔔 We want to keep it as open and collaborative as possible. So don't hesitate to add valuable stuff with a fork + PR! 🔔
Some notable one-off articles not added to the list above:
So here's my TL;DR for you folks:
- If you don't know the underlying principles of the web, you'll eventually hit a wall thanks to the evolution of the language itself and the constant arrival of new frameworks.
- Knowing pure JS will make you a key engineer who can solve complex problems (reason before frantic searching).
- It'll make you versatile and productive, both on the front-end and back-end.
- It'll give you the toolset to innovate, not just execute.
- It’ll guide you on when to use a framework or not.
- It'll give you a better general understanding of how browsers and computers work.
Using a JS framework can surely bring you somewhere fast. But it won't bring you far if you don't understand the core concepts behind it. Just like learning to play Wonderwall on the guitar won’t teach you how to compose music, but it’ll give you a reason to practice.
I firmly believe that this "learn the basics/roots first" principle applies to pretty much everything in life. From learning a new programming language to starting a new sport. It requires a lot of practice, but once you master it, the only thing left to do is to get creative with it. And that's where the real fun begins.
Enjoyed the post? Hit the share buttons below!