I already feel that way with some features of ES6 and typescript - though both have more benefits than negative attributes, sometimes there are more than one wa

I already feel that way with some features of ES6 and typescript - though both have more benefits than negative attributes, sometimes there are more than one way of doing things, which introduces a little mental overhead when reading code, and the overhead compounds over time. For example, types vs interfaces in typescript - they can be used interchangeably in many cases, and not in a few other cases. [1] Let's KISS, not over complicate for the sake of more features that may be negligible in value. And let us especially not introduce features that can overlap. [1] Example: "A class can implement an interface or type alias, both in the same exact way." - https://stackoverflow.com/questions/37233735/interfaces-vs-types-in-typescript https://stackoverflow.com/questions/37233735/interfaces-vs-t...