this post was submitted on 08 Sep 2023
57 points (70.2% liked)
Programming
17502 readers
17 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The summary uses the term "vanilla JS" in a weird way. It's just to further denote it's not TypeScript because TypeScript is a language that essentially extends JavaScript. It's not a framework. This is about language choice of TS vs JS inside large complex libraries only.
Libraries tend to have a need for generic typing due to the nature of being code used by other code. So you get a lot of syntax craziness involving Type parameters.
You can still use the libraries mentioned in a TS project. They're just not written in TS. TS and JS can be in the same project. Moreover, it even states this isn't about developers using TS in non-library projects.