Skip to content
This repository has been archived by the owner on Dec 11, 2021. It is now read-only.

Why to avoid class: composition vs. inheritance #7

Open
jnv opened this issue Jul 28, 2015 · 0 comments
Open

Why to avoid class: composition vs. inheritance #7

jnv opened this issue Jul 28, 2015 · 0 comments

Comments

@jnv
Copy link
Contributor

jnv commented Jul 28, 2015

Revisiting the guide a some of this stuff is primarily an opinion without substantial reasoning. Case in point is the recommendation to avoid ES6 class. For me the primary reason is that it invites reliance on inheritance and hinders composition, which is actually described in few of Elliot’s articles (and raison d'être of stampit). I should add it in later revision.

(But to be absolutely honest, my primary objective with such an opinionated guide is to push devs out of their comfort zone and rethink practices before they repeat the same mistakes we are doing in other languages. They can disagree, but they need to think why.)

@jnv jnv changed the title Why to avoid class: composition vs. class Why to avoid class: composition vs. inheritance Aug 1, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant