3 ms·

I've been thinking about doing something like this for the past few months, kudos for giving it a shot! I disagree with your statement: "Don't use the plain va

I've been thinking about doing something like this for the past few months, kudos for giving it a shot! I disagree with your statement: "Don't use the plain vanilla approach until you've tried some of the popular web development frameworks and have learned why you might want to do without, and until you're confident on how to structure a codebase without the help of a framework." I was writing vanilla javascript for years before I began using frameworks, so when I encounter a new one, I understand exactly what problem it's trying to solve. For any beginners, I personally recommend just building websites directly, without any framework assistance.

Joeri 2y ago
It is a tricky balance to be sure. Building familiarity with html, css and javascript first is necessary, and I do link out to tutorials that teach that on the welcome page. But beyond the basic knowledge, how do you learn good practices quickest? Do you start trying things and learn what works and what doesn’t through experience? Or do you follow the learning track of popular frameworks and learn good practices through example and osmosis? On balance I think it’s better to learn how to build with frameworks first to learn all the right concepts in the guiding structure that they provide, and only then to walk away from frameworks and have complete freedom by going vanilla. That’s why that paragraph is there. YMMV.