1- What is confusing about platforms?
The parts of each platform/framework that I failed to really grasp was firstly the syntax conversion. Learning some of the individual syntax of each framework was a hassle and the resources available for learning are not particularly digestible for newcomers. The second part was how each platform fit it's niche and why there were so many conventions for the same task of web development.
2- How could web components and VanillaJS standards be taught in a way that is more approachable?
Breaking it down bit by bit and explaining the reasoning behind each part of the process of making a full web page using JS/Web components would be ideal. A platform that does a good job of this would be W3 schools, as they also provide the ability for newcomers to return to their website as an information hub for all basic syntax and logic related needs.
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)
None of them were easy to work with, but the least complex was Vuejs simply because there were not as many syntax changes as compared to vanilla JS. I like web components, but each little node required to get everything working left me and some others a bit lost in terms of how to accomplish each specific thing.
4- Think back on the tooling. What parts were confusing? What clicked with you immediately?
The confusing parts included implementing concepts like css variable states, importing other tools like meme maker, the shadowroot and working around it, and the building process (npm, all the selection options when making a new project, why the vercel build was not loading and it's errors), and finally the individual rendering and assignment methods (render(), properties, reflect, constructor(), export,
The understandable parts included HTML and CSS and they don't differ much from vanilla on each platform, as well as Vanilla JS although it took a lot more time than the latter two. Where to include things in the file architecture was also self explanatory after the first few times (where to put html css)
5- What additional readings did you have to do in order to make sense of things.
When doing the remediations to fit our individual card requirements, I found myself going to youtube videos (class videos mostly, along with others that explain specific functionalities of a method for example). In terms of readings, it was hard to derive anything exactly from stack overflow but occasionally other forums like Mozilla developer web docs did a good job explaining confusing concepts.
Top comments (0)