Reservations About TypeScript
class and prototypical inheritance are understood, it shouldn’t be a big problem, but I think it needs to be pointed out, so as to not cause confusion (and weird bugs!) down the road.
TypeScript brings some great features, but, in my opinion, it comes with some significant pitfalls that need to be addressed and realized before jumping in with both feet.
I’m definitely more open to using it than I was a year ago. In part, this is because I’ve used Visual Studio Code and immediately fell in love with the autocomplete for TypeScript properties/method signatures. It’s such a nice change from having no autocomplete and I can totally see myself becoming spoiled using Visual Studio Code. However, I think the same reservations I had a year ago still ring true. Maybe after using it more in depth over the next year, I’ll have changed my perspective, but for now, I still have some concerns about it. Maybe this is me just worrying about something that’s not actually as big of an issue as I perceive it to be. Maybe I’ll be writing another post a year from now praising TypeScript. I’m not sure, but for now I still hold to (mostly) the same opinion I did a year ago.