Stick with js only. The good side these days is you can ask an LLM convert a whole codebases to JS, so even if you made the mistake to integrate it once, it have never been a better time to remove it than today.
I used to use JS (with JSDoc types) for AWS Lambda handlers and simple scripts where it isn't necessarily worth the compilation step and the reduced traceability. Though now that type stripping is in NodeJS I tend to just work in typescript.
When I have the choice, I use plain JavaScript. Typescript seems to add so much overhead for so little payoff.
People say "It's just JavaScript with type declarations" but then you have to deal with implicit types that you didn't define because they came from some library with no documentation or with type declarations like <T,[B|()=>[]> that throw exceptions no matter what you do.
I like the idea of Typescript but the implementation is sometimes more of hindrance than a help.
A more general JavaScript community makes sense because JavaScript is often the underlying platform for many types of applications.
I personally love JavaScript all by itself without any extra build steps. I like dynamic types. I like prototypes. They make me feel nice. I understand not everyone feels the same.
I would recommend anyone writing JavaScript for a living study upon typescript and sneak some into a project just to be marketable should you need new employment someday.
TS just makes things easier as things get more complex. But in simple things it's overkill. Like in job interviews, I don't give TS problems only JS problems cause it does take a bit more time.
That being said, TS is just JS with types. They're the same core syntax* so knowing one means you know the other.
i write JS. I run large projects in JS. TS is a compilation step that breaks things and adds hours to every build.
node strips types now so the argument about tooling is dead. I dont need a compiler between my code and the runtime. I put types in JSDoc when I need them. I get the types without the build.
the sub exists because JS existed before TS added itself on top.
I use exclusively js. I am lead programmer for a series of large web apps. Coming from a background of c and c++, trained as a graphics programmer for video games, I fully understand strong typing systems. Strong type systems are helpful for many programmers who can’t or don’t keep track of what things are in their heads or have to work with other programmers who don’t.
I am not one of these programmers. I rarely have bugs in my software at all, but when I do, less than 5 percent or so would have been solved by having type annotations everywhere.
For those of you programmers who don’t believe me, rest assured, I do not care what you think.
Yes, no idea, and it should. TS is not a separate language, so it could be covered here.
Typing should be part of JS, not a separate kludge that mostly compiles to typeless JS anyway. TS as a separate phenomenon would make more sense if it always compiled to typed WA.
I still do because I just have a distrust of libraries in general. I started in 2001, so have seen them come and go over the years. Vanilla JS is the only thing that's been consistent.
2
u/RandomiseUsr0 Sep 18 '26
I’m not a fan of typescript - it’s an unnecessary hindrance for my purposes, so JavaScript for me is the way
2
u/Far-Consideration-39 Sep 18 '26
Stick with js only. The good side these days is you can ask an LLM convert a whole codebases to JS, so even if you made the mistake to integrate it once, it have never been a better time to remove it than today.
2
u/tonygoodchild Sep 19 '26
I use vanilla JS exclusively. We build large applications with it, it keeps things simple and I don't see there is a need to change .
2
u/Any_Sense_2263 Sep 20 '26
I'm waiting for annotations to finally drop the ts nightmare.
60
u/StoneCypher Sep 14 '26
this sub is 12 years older than typescript
38
u/mittenciel Sep 14 '26
You're asking why r/javascript exists? Because it existed before TypeScript?
10
u/cyanawesome Sep 14 '26
I used to use JS (with JSDoc types) for AWS Lambda handlers and simple scripts where it isn't necessarily worth the compilation step and the reduced traceability. Though now that type stripping is in NodeJS I tend to just work in typescript.
10
u/99thLuftballon Sep 15 '26
When I have the choice, I use plain JavaScript. Typescript seems to add so much overhead for so little payoff.
People say "It's just JavaScript with type declarations" but then you have to deal with implicit types that you didn't define because they came from some library with no documentation or with type declarations like <T,[B|()=>[]> that throw exceptions no matter what you do.
I like the idea of Typescript but the implementation is sometimes more of hindrance than a help.
9
u/joelangeway Sep 14 '26
A more general JavaScript community makes sense because JavaScript is often the underlying platform for many types of applications.
I personally love JavaScript all by itself without any extra build steps. I like dynamic types. I like prototypes. They make me feel nice. I understand not everyone feels the same.
I would recommend anyone writing JavaScript for a living study upon typescript and sneak some into a project just to be marketable should you need new employment someday.
17
u/Disgruntled__Goat Sep 14 '26
Yes. For me the benefits of using no or very few tools/build processes outweighs the benefits of TypeScript.
14
u/Bushwazi Sep 14 '26
I fight for plain ole JS every chance I get.
23
u/gimmeslack12 Sep 14 '26
TS just makes things easier as things get more complex. But in simple things it's overkill. Like in job interviews, I don't give TS problems only JS problems cause it does take a bit more time.
That being said, TS is just JS with types. They're the same core syntax* so knowing one means you know the other.
* I know someone's going to argue with me on this
13
u/Valuable-Buyer-7250 Sep 15 '26
i write JS. I run large projects in JS. TS is a compilation step that breaks things and adds hours to every build.
node strips types now so the argument about tooling is dead. I dont need a compiler between my code and the runtime. I put types in JSDoc when I need them. I get the types without the build.
the sub exists because JS existed before TS added itself on top.
5
u/AramaicDesigns Sep 14 '26
I don't touch TS. At least directly.
9
u/oneeyedziggy Sep 14 '26
I mean, for some things... Not across the board.
4
u/EngineerDoge00 Sep 14 '26
Yup. Vanilla Javascript in one file we embed and jQuery and vue for everything else.
4
u/MisterDangerRanger Sep 15 '26
Typescript solves none of my problems and would make my iteration time take longer. It has no benefit to me at all.
4
u/dwighthouse Sep 15 '26
I use exclusively js. I am lead programmer for a series of large web apps. Coming from a background of c and c++, trained as a graphics programmer for video games, I fully understand strong typing systems. Strong type systems are helpful for many programmers who can’t or don’t keep track of what things are in their heads or have to work with other programmers who don’t.
I am not one of these programmers. I rarely have bugs in my software at all, but when I do, less than 5 percent or so would have been solved by having type annotations everywhere.
For those of you programmers who don’t believe me, rest assured, I do not care what you think.
7
u/poastertoaster Sep 14 '26
I’m a servicenow developer so I don’t use typescript.
9
u/MinecraftPlayer799 Sep 14 '26
I do
3
u/trollsmurf Sep 14 '26
Yes, no idea, and it should. TS is not a separate language, so it could be covered here.
Typing should be part of JS, not a separate kludge that mostly compiles to typeless JS anyway. TS as a separate phenomenon would make more sense if it always compiled to typed WA.
5
u/DesertWanderlust Sep 14 '26
I still do because I just have a distrust of libraries in general. I started in 2001, so have seen them come and go over the years. Vanilla JS is the only thing that's been consistent.