Live data from Hacker News

TypeScript is now officially 10 years old

coderoasis.com

21–30 of 207 posts

Re: TypeScript is now officially 10 years old

#21

Earlier quoted context omitted.

that's maybe the second or the third most important factor. the first is aggressive marketing that microsoft does for its products.

That unfortunately hasn’t helped C# become more popular outside of Microsoft legacy shops even when it did go cross platform and open source.

Well the fact that it was available solely on Windows for so long was its doom.

Actually I thought of using C# a few months ago, and I was like "Oh wait, does it even work on other platforms than Windows now?". Sure I'm not a C# developer, so I'm not up to date on C# news, but that's an issue if your goal is to drive adoption. Everyone that has heard of C# should know that it's now cross-platform.

Re: TypeScript is now officially 10 years old

#22

Earlier quoted context omitted.

that's maybe the second or the third most important factor. the first is aggressive marketing that microsoft does for its products.

That unfortunately hasn’t helped C# become more popular outside of Microsoft legacy shops even when it did go cross platform and open source.

C# is extremely popular, maybe just not in your particular field.

Re: TypeScript is now officially 10 years old

#23
post #9

>TypeScript never set out to build a separate, distinct, and prescriptive language. Instead, TypeScript had to be descriptive. Sadly, the majority of people writing Typescript rarely care about descriptive and readable code these days. Somehow the focus shifted from using types to better understand complex systems through the code itself , to writing whatever polymorphic union type abomination that yields the best In…

This. Probably every TS codebase I ever worked in had zero to none function- or inline docs with people always claiming "documented by TS". I call that BS, and you can see that in their projects. "Typescript codebase" became the equivalent of "generic low quality codebase" imo.

I'll never understand why people need a programming language inside a programming language and refuse simplicity (i.e. using jsdocs, which has perfect IntelliSense support).

Re: TypeScript is now officially 10 years old

#24

Typescript is for big project and team collaboration. JS is still my choice for personal or small project. Fast!

> Typescript is for big project and team collaboration.

TypeScript is for any kind of project, it just makes your code safer, easier to debug, easier to read / come back to in the future, etc.

> Fast!

That doesn't mean anything.

Especially for a small project, the TypeScript to JavaScript compilation will take milliseconds, there is no speed impact at all.

Re: TypeScript is now officially 10 years old

#25

Earlier quoted context omitted.

that's maybe the second or the third most important factor. the first is aggressive marketing that microsoft does for its products.

That unfortunately hasn’t helped C# become more popular outside of Microsoft legacy shops even when it did go cross platform and open source.

C# and ASP.NET Core feels like the default stack in Western Europe, even among startups. You have to look harder to find companies using Node.js, Rails, Django etc.

Re: TypeScript is now officially 10 years old

#26
post #9

>TypeScript never set out to build a separate, distinct, and prescriptive language. Instead, TypeScript had to be descriptive. Sadly, the majority of people writing Typescript rarely care about descriptive and readable code these days. Somehow the focus shifted from using types to better understand complex systems through the code itself , to writing whatever polymorphic union type abomination that yields the best In…

This. Probably every TS codebase I ever worked in had zero to none function- or inline docs with people always claiming "documented by TS". I call that BS, and you can see that in their projects. "Typescript codebase" became the equivalent of "generic low quality codebase" imo. I'll never understand why people need a programming language inside a programming language and refuse simplicity (i.e. using jsdocs, which ha…

This is entirely applicable to JavaScript codebases, except that at least in typescript you have less reverse engineering work to do.

If you want to have documented codebases, work with people who document their code. You’ll find that typescript doesn’t always mean undocumented, and incidentally you’ll find that documented doesn’t mean high quality.

Most high quality codebases in the JS ecosystem after 2016 ish are in typescript.

Re: TypeScript is now officially 10 years old

#27
post #2

The post mentions one of the most important factors in TypeScript’s adoption: it launched, from the start, with good tooling.

I tried using Flow at some point when TypeScript was much newer and wasn't the obvious choice for typed Javascript yet. I couldn't get it to work properly. I probably could have with more effort, but I didn't feel like I would be able to keep it running well and debug issues if they would arise.

Re: TypeScript is now officially 10 years old

#30
I was unsure of Typescript at first, but it has become an absolute joy and absolute pleasure to develop in.

I was reluctant to introduce a build step (having got used to the simple refresh cycle of a browser plus vanilla javascript) but I am pleased to say that this is a bit of a non-issue now with modern tooling like esbuild et al.

I still avoid NPM like the absolute plague, but the good news is that tooling like Deno have made typescript first server-side development in the ECMAScript world a total joy.

I've said it before - it's like floating through the air. So serene, so expressive. A true joy.

Post reply on HN