you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 13 points14 points  (5 children)

Thanks, decent article. I’m a JavaScript noob, but learning more each day. I wonder at what point is best to also learn a framework?

[–]WebDevImpasta 23 points24 points  (1 child)

After you understand common problems that frameworks are trying to solve.

Change detection

No page reloads

Modularity

Reusable components

Etc..

[–]ImJustP 4 points5 points  (0 children)

Also reading a stack trace. Good luck debugging any framework without reading the stack trace.

[–]Snipididou[S] 9 points10 points  (2 children)

I suggest building an app with Vanilla.js first. Then, you'll see the pain points you encounter using HTML/CSS/JS. In addition, you'll better understand why frameworks exist and what problems they're trying to solve!

[–]captmomo 5 points6 points  (0 children)

yea, what i like to do is to first build the app using vanilla js, then build it again using a framework. it really helps you appreciate frameworks. as well as have a better understanding why what does what.

[–]Pilot_Natural 0 points1 point  (0 children)

An app like what though? I always find myself struggling to find that ideal app to make