4 ms·
There's a historical reason why classes are used a lot for models. It's up to you to decide if this reason applies to your project or organization. A few years
by brlewis 7y ago
There's a historical reason why classes are used a lot for models. It's up to you to decide if this reason applies to your project or organization.
A few years ago there was a dilemma between ES6 and TypeScript. A lot of JS developers chose to stay away from TS in order to follow the ES6 path instead. Then TS harmonized with ES6. But it retained a reputation for being an incompatible alternative to ES6 rather than just JS+type annotations. However, if you write classes, they look just like ES6 classes plus type annotations, allaying concerns.