Why Typescript is getting cancelled?

Typescript is getting cancelled! Learn why big projects are shifting to JavaScript, and why you should too. This video is a detailed breakdown of how Typescript does more harm than good, and what alternative can you use instead.
Timestamps
0:00 - Intro
0:54 - Rise of Typescript
2:00 - Advantages of Typescript
2:54 - Downsides of using Typescript
6:03 - What to use instead?
Socials:
Twitter - / rituraj_io
Subscribe here - www.youtube.com/@TheAntiNerd?...
#javascript #typescript #jsdoc #coding #webdevelopment

[@exe2543]

I mean the editing of the video is good, but I don't really think the downsides listed are that significant. I think the benefits still far outweigh them.

[@TheAntiNerd]

Unless you have a huge project, you can just get away with most of the downsides. Once things start to scale, it crosses a point where TS becomes a problem. Thankfully one can just switch to JS Doc like us and enjoy the benefits of both the worlds.

[@redcodemohammed]

Spent a month migrating because the build time was an entire minute wow, you made me remember a meme that says (spend hours to automate a 5-minute task). And yeah I don't know why you mentioned logical errors? what does TypeScript do with them anyway? Nobody said you can't get away with not testing your code. And by the way, 5:58 made me sure you don't know how to use TypeScript.

[@TheAntiNerd]

The problems we faced are well defined in the video, and a few things are not. Either way, we are aware of the advantages and our users are reaping the benefits of this change. Can't say I mastered Typescript, but I like to think you need to know at least something about what you are doing to build a 7+ figure business.

[@josersleal]

question #1 is why do you even use js??? is this 1990? #2 why did you not simply trasnpile (neither js nor ts compile to anything) and instead rewrote the code? Or paste it into some gpt crap? You biggest problem is th ecompile time of the entire thingy? why do you care? youre supposed to only compile everythign if deploying and to isolate when coding. youre doing it wrong imo.

[@TheAntiNerd]

#1 JS is light weight. Runs out of the box. I see no problem there. #2 The code base is quite huge to use ChatGPT, and we cannot risk the AI hallucinating on us. Also just using the compiled version of TS wasn't the way to go since it has no type definitions that would be allowed by JSDoc and we also had to make a bunch of other changes, so figured that writing it from scratch would be the way to go forward. Moreover, it was not only that compile time is an issue (which it is) but on a big project like this, it ends up consuming a lot of resources. Upwards of 4GB of RAM is a must and 6GB - 8GB recommended. Which is hilarious since the actual JS code needs < 1GB of RAM to run. The decision was hence influenced by not just "tech" and "code" (for the sake of building tech alone, as I mentioned in the video), but was made keeping in mind other aspects of the business like money, scalability, collaboration, and so on.

[@leonss2356]

@@TheAntiNerd ??? why would it need any more RAM than JS to run? it *_is_* JS

[@TheAntiNerd]

​@@leonss2356 The stage where you run 'tsc' to convert your TS files to JS, is when most of the time and resources are consumed. Again remember, this is only noticeable and causes a problem in big projects like the one we have. We would constantly run into heap out of memory issues, and we had to not only upgrade our servers, but also run `tsc` like this. node --max-old-space-size=4096 /usr/local/bin/tsc --incremental It only ever compiled when at least 4096 MB of RAM was allowed, and even then, it would sometimes crash, and we had to restart the server.

[@leonss2356]

@@TheAntiNerd ok, i just don't see what _JS needing less than 1GB RAM to run_ have to do with _TS transpilation taking 4GB or more_ . Transpilation is not runtime.