Popular posts

Could you elaborate a little why to skip JS frameworks?

This is a good advice. As for Dominik, from my perspective I've been in JS my entire carrier. I still don't know 'ES5' properly. ES6 and all the gotchas in its sub optimal design? forget about it..

It is not just the syntax but also the order and context where you use the things you learn. Learning a language properly is a very difficult asset which is in my view acquired by a few people on earth.

Frameworks are good, but the list of 'homework' that needs to be done till that point I think is some sort of a rabbit hole, unfortunately

Ibrahim Tanyalcin basically answered the question for me.

A framework, at the core, is a "key to the city" that is usually misused and abused.

One of the examples I always throw forward is the fact that frameworks are meant for consistency within a collaborative environment. This works in-house, most of the time, with A-List players who intend to stick with the project long-term. It's built by them, for them, with the goal of making things quicker and DRYer for their team, and vice-versa.

It never seems to happen with established JS frameworks, though, since it will take most honest developers more time to understand and utilize them correctly than it would for them to learn and work with Vanilla JS. And this is the catch; You really need to know Vanilla JS, along with having an intermediate to advanced understanding of it, to work "magic" with a JS framework. And, during that process, you will repeatedly ask yourself, "Why?" when you come across issues that simply don't make sense from a fundamental POV.

If proper collaboration was really a key selling point... why are there so many JS frameworks still popping up? No one feels the other approach will be as effective as their own - which is the complete opposite of "...working with someone to produce or create something." The popularity of many frameworks was encouraged by clueless agencies that saw they had "bigger packages" to sell to companies - no matter what the cost. And, they want things to break down the line (from outdated dependencies, etc.) so the client keeps coming back. This is also one of the problems with Wordpress, in which a single update will often break tons of plug-ins and custom code.

With programming languages like Go, which is the first to utilize multiple processors, along with Google and the co-creators of Unix behind it, moving from Node.js/Express seems like a natural evolution, and a great addition to your growing skill set. Both are very different, but quite similar in many respects - plus Go has a few more years to go before it will be seen as something more beneficial by the general public. Ironically, in an interview, a co-founder of Wordpress said that he'd like to rewrite it in Go.

Also, to be fair, Express is a framework - however - it's a server framework, and super-flexible to the point of being able to make your own with it. A great example of an upscaled Express is Sails.js.

I can go on forever, since the subject always starts great discussions and an occasional debate, but the thing to keep in mind is that you should never let libraries and frameworks control your approach to any project...

You control the code, and less bloated it is, the better your product will be.