![On being a “JavaScript framework developer”…](https://res.cloudinary.com/dfcwuxv3l/image/upload/w_1280,h_669,c_fill,q_auto,f_auto/w_900,c_fit,co_rgb:232129,g_south_west,x_70,y_160,l_text:oswald_84_bold_line_spacing_-34:On%20being%20a%20"JavaScript%20framework%20developer".../w_900,c_fit,co_rgb:232129,g_north_west,x_70,y_540,l_text:ubuntu_38:@stefanjudis/stefan-judis-website/social-image-with-new-dude "On being a “JavaScript framework developer”…")
Creating “vanilla web sites” moved out of the mainstream. Right now, a complete trade focuses on doing issues with a selected framework. And that is solely logical.
Attain for the mainstream framework, and also you get developer productiveness free of charge! They are saying. Should you want a brand new characteristic, something is just one npm dependency away.
Each web site I’ve labored on within the final years (perhaps even a decade?) is annoyingly complicated (and brittle). Do you want a sticky header — npm set up. Do you wish to validate a kind — npm set up. Do you wish to present a modal — npm set up…
The result’s bloated web sites constructed by framework builders. And you’ll’t blame all the brand new builders for that. When all of the job postings require framework expertise, folks becoming a member of the net dev world give attention to changing into framework specialists.
Nonetheless, is specializing in one specific framework the perfect method?
This is Maximiliano Firtman with some wisdom:
[Framework] builders are much less snug transferring between frameworks and libraries.
[Framework] builders don’t have a full understanding of how the browser works, what it presents, and what “magic” their framework offers.
[Framework] builders typically depend on a restricted toolbox, utilizing the identical answer for each downside, even when it’s not essentially the most environment friendly choice.
Typically we find yourself utilizing the flawed answer for an issue, resulting in gradual consumer experiences and an excessive amount of complexity.
Figuring out the DOM, fashionable CSS and semantic HTML is invaluable for constructing good web sites! Normal net dev information will result in a greater, sooner and extra accessible net.
I would love the trade to follow Alex Russel here:
By no means, ever rent for JavaScript framework abilities. As an alternative, interview and rent just for fundamentals like net requirements, accessibility, fashionable CSS, semantic HTML, and Net Elements.
A dev figuring out the net platform will produce nice web sites whatever the tech stack. On the finish, there’s “simply” net stuff beneath all of the framework magic, proper?
A framework developer, then again, might need a tough time switching frameworks, reaching for easy options or delivering high-quality web sites with out the complete JavaScript ecosystem. And I’ve seen this precise downside loads of occasions.
So, in the event you can, give attention to changing into an online developer relatively than a framework developer! And in the event you’re hiring, give attention to bringing folks on who know the net. They will be a a lot greater assist if you migrate your website to the following trending framework in 5 years… (and everyone knows it’ll occur).
