- cross-posted to:
- typescript@programming.dev
- cross-posted to:
- typescript@programming.dev
I never met someone that actually used Typescript in a professional setting saying they dislike it. It makes your life easier and you can still have parts of your project using regular JS.
good. typescript has always caused us more headache than it worth in all my projects. I bill my clients extra for it if they make me work on it.
Clickbait - The silent killer
Soon on Netflix (probably)
Tl;dw: it’s too much “type-gymnastics” when developing a library.
The title makes it seem like it’s a wide spread thing in the industry but according to the video it’s 3 frameworks.
Yeah, it’s additional work but I’ve found that really convoluted or complex type definitions usually mean you should consider refactoring. Of course this is a bit different when it comes to developing frameworks where you might want to support a bunch of different use cases.
Maybe I’m biased because I’ve been using TS ever since it first came out.
Opinion from me, a JS beginner: Vanilla is good enough now. If your IDE lets you type common structures like
document.getElementById("")
with shortcuts, I find no need to use a framework. Also, vanilla works better in offline projects.