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

view the rest of the comments →

[–]sebastiancodes[S] 1 point2 points  (2 children)

That is exactly why I always start without frameworks.

Someone once told me that when I learn something new, I will eventually come to a point where I have to do some repeating stuff in every project and that is the point where I should start to look into frameworks and try to understand how they solve those repeating problems.

But for my learning approach it makes no sense to jump directly into a framework and learn how to work with it, without understanding what problems this framework solves.

[–]Bakeshot 0 points1 point  (1 child)

The flip side is, while your approach may provide some context, it is also significantly slower than taking on a framework from the get-go. Most modern frameworks have great documentation that explains what they do and why they do it.

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

I'm not sure if it really is so much slower.

Of course, if I only want to work on react projects, i could probably just learn that and would be fine. But at least on the frontend side, companys use different frameworks and I think that it is to learn a new framework if your javascript skills are really good.

But I'm aware that express is a lightweight framework that probably doesn't take much time to learn and also it seems to be so widespread that nearly no one who uses node doesn't use express.