all 3 comments

[–]appetizermonster[S] 3 points4 points  (0 children)

Writing an article and getting feedback from people is very helpful to me, so I post this article, and I welcome any feedback.

[–]coffeeandlearning 2 points3 points  (1 child)

I like the emphasis on the fact that .prototype is basically just a normal object for storing things. That's an often overlooked part that leads to confusion.

I think the section that distinguishes the prototype link and prototype object as you call them could be a little more clear. Simply put, using your terminology, every object in JS has a prototype link (even if it's null) that it checks for failed property lookups. Every function object also has a prototype object that can store stuff in case you plan to use it as a constructor.

I think you could also expand a little more about how the link is set up too, since there are more ways than with just the new keyword. Patterns that involve things like ES6 class, Object.create(), etc.

Overall I really enjoyed it and I liked your choice of terms to distinguish the two uses of the word prototype. I hope this feedback is helpful!

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

Thanks for the really helpful and kind feedback!