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

Why to avoid class: composition vs. inheritance #7

@jnv

Description

@jnv

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.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions