A. Matías Quezada
Jul 28, 2017 · 1 min read

I agree with the `.of()` argument but I don’t think to recommend people to not use classes is a good pattern.

I hate ECMA added classes to ECMAScript but now they are in and I do remember the times when we had no standard way to split our app in components and every library had it’s own “createClass / createChunkOfCode” method. That was caos and I don’t want to return to that.

We have to stick with one option so we all can share code and use it without learning “how to get an instance from this component”. If classes are more performant, common knowledge and the new language standard we should stick with it. Having two patterns create components will only make things more complex.

    A. Matías Quezada

    Written by