Open dissidently opened 8 years ago
@dissidently Yes, article really need some editorial assistance
It is an achievement in its own right. There is no other exhaustive and direct attempt (that I can find) to clarify all these things in anywhere near the clarity and earnestness you're doing. I "forked" and have done some more editing. But I still need to understand JavaScript more fully. I'm not completely grokking prototypes and its constructor ideas, yet.
I may need to ask you questions about how to think about aspects of JavaScript to best edit what you're saying, sometimes. Apologies in advance. I'm not a programmer. Design is my limit.
Ok, let's do it
"This is a beginner-level post, just to clarify and visualize JavaScript prototype-based inheritance."
could be:
"This is a beginner level post to clarify JavaScript prototype-based inheritance via words and diagrams."
"A lot of incomplete and even wrong info can be found on Internet about JavaScript prototypal inheritance. I will just try to explain it again with help of diagrams."
could be:
"Much online information about JavaScript prototypal inheritance is scattered, wrong, confusing and misleading. This explains it as clearly, truthfully and easily as I can with clear images and words."
"JavaScript inheritance understanding is important, even if you are not going to use JavaScript OOP patterns, since many of language built-in functionality based on inheritance."
could be:
"Understanding JavaScript's inheritance approaches is important because the core tenets of its design and operation have been designed around its OOP patterns and abilities. Even if you don't plan on using these it's illuminating to understand the origin and reasoning of the language's methodologies."
"I am not advocating of using OOP patterns and "classical"-like inheritance in JavaScript at all. I personally prefer using "factory" and "mixin" instead of a "constructor" pattern. But this post is not about patterns, it is only about JavaScript prototype-based inheritance mechanics visualization."
could be:
This article is clarification of prototype-based inheritance mechanics and understanding them through visualisation. My personal preferences for use of "factory" and "mixin" over "constructor" patterns does not colour the article. I am not advocating use of OOP patterns and "classical"-like inheritance in Javascript.