1) What is confusing about platforms?
What's really confusing about frameworks and stuff is that some of them have very different syntaxes and way of doing things. When you are first learning web development stuff, they start you off with the basics. But as you begin to explore frameworks, some of them will have you unlearn things to learn the new way that the framework handles it. Once you are done with that framework and come to use something else, you may find that some of the syntaxes and tooling in your previous framework doesn't exist in others.
2) How could web components and VanillaJS standards be taught in a way that is more approachable?
I like the idea of hands on teaching. I feel that bookwork is important and all, but I believe nothing beats sitting down and actually practicing it. Having hands on work with the basics of VanillaJS is my best bet. Properly splitting up the standards and work is also important because you don't want to make things seems unapproachable because of their complexity. Start of with the basics, and keep building the complexity as you go. I really just feel that we shouldn't overcomplicate the easy problems when first learning. I also don't like the idea of creating highly specific and framework exclusive questions. Having a single standard agreed upon may seem impossible currently, but I feel that would be very beneficial to beginners like me. Rather than being told that this is how this framework might do this, but only for this framework.
3) What did you find easiest to work with on 1st stab? (You don't have to say web components, this is an honest take, if it was Vue cool, but justify it)
I personally found Vue the easiest to work on as a new developer. When I first began working on vue, it was very easy to identify which file I had to edit. It was called HelloWorld.vue which to me seemed like a dead giveaway. It also helped that I was able to put all my HTML, CSS, and JavaScript in one file.
4) Think back on the tooling. What parts were confusing? What clicked with you immediately?
The entire idea of tooling is still kind of fuzzy to me. My best guess right now is that it is referring to the different features that different platforms and frameworks bring. It seems like fancy new features that make life more easier in some situations. It clicked to me pretty quickly why the author of the article wanted to minimize tooling. Since this complicates things and creates highly specific framework only problems and solutions.
5) What additional readings did you have to do in order to make sense of things.
https://www.sitepen.com/blog/intro-to-html-first-frontend-frameworks
I read this article to help me understand the HTML first approach. I like the idea of shipping portions of HTML separately to at least be able to ship functional product. Then the fancy interactive bells and whistles separately. Since users should at least be able to access the content first, then they can worry about interactivity.
Top comments (1)
Hey Aaron, thanks for sharing and welcome to the community! :D
Hands-on learning is absolutely my favorite way of learning - like you said "bookwork is important and all" but I've found nothing truly beats just diving in and building (and breaking) things
Also it all comes down to having a solid grasp on the fundamentals 😎 Syntax, idioms, and best practices might change framework-to-framework but if you build a strong foundation with the language of your choice (such as vanilla JavaScript) you'll find the transferrable skills you gain will pay back tenfold as each framework becomes just another tool in your toolbox
Best of luck on your journey!