[jmull]

You heard wrong.

The only way typescript is going away is if JS essentially incorporates it.

The only things people don't like about it is that you need some tooling and a build step.

However, with its popularity, ts is built in to a lot of things, so the tooling usually isn't a big burden (particularly to get started).

And it's viable in a lot of cases these days to forgo the build step and instead use JS with typescript type annotations. (That might be what you heard about. That's really still using typescript, though.)

[leptons]

>The only things people don't like about it is that you need some tooling and a build step.

Wrong. Many people dislike many things about Typescript.

https://levelup.gitconnected.com/the-inevitable-decline-of-t...

https://medium.com/codex/why-are-javascript-pros-saying-good...

https://gomakethings.com/ditching-typescript-for-javascript/

https://www.reddit.com/r/sveltejs/comments/12cyady/are_you_l...

There are plenty more examples of why people tried typescript and went back to javascript. It's definitely not only because of a build step, but also "type gymnastics", and other code bloat.

[csjh]

Claiming "many people" and proceeding to link to 4 posts that use Svelte as an example is a bit silly considering Rich Harris has said, numerous times, that the decision in Svelte's codebase should NOT be taken as advice for what to do in your codebase, because their decision only pertains to a very specific set of circumstances.

[leptons]

I was countering the previous comments assertion that "the only reason" people don't like typescript was because it has a build step, and your comment doesn't prove me wrong.