Any survivors of https://www.typescriptlang.org/docs/handbook/esm-node.html wanna share their experiences?
type module in the package.json, and import every and all .ts file with a .js extension. zero problems for a year or two.
TypeScript is now officially 10 years old
41–50 of 207 posts
Re: TypeScript is now officially 10 years old
#42Quoted post unavailable.
> When people say, like, "blah blah VSCode this blah blah TypeScript that", all I hear is "Embrace, Extend, Extinguish the open Web ecosystem".
Your memory may be too long to fit the TypeScript demographic.
Re: TypeScript is now officially 10 years old
#43Re: TypeScript is now officially 10 years old
#44Earlier quoted context omitted.
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.
“My field” is a 20+ year MS ecosystem developer from C++/MFC, VB6, .Net Compact framework, .Net Framework, .Net Core, etc.
As I said, very few new companies that aren’t “legacy” shops are choosing .Net.
In my current job in cloud consulting at $BigTech, almost all of the .Net projects that come through are older companies compared to newer companies that are using non compiled languages.
These days I write in almost any language they prefer among the popular languages.
Re: TypeScript is now officially 10 years old
#45The post mentions one of the most important factors in TypeScript’s adoption: it launched, from the start, with good tooling.
In my opinion the most important factor was that it is a superset of JS and any valid Javascript code is/was valid TS code. That allowed for gradual adoption and you didn't have to risk going all-in into new technology.
Also the `any` type [1]. It makes porting an existing project ridiculously easy: just type everything as `any`, and it also gives freedom to the developer to think in code when developing, trusting that they (will) know what they are doing, instead of screaming at the smallest mis-type with annoying bright red squiggly lines.
It is so liberating to type a variable as `any` when sketching new code, figuring things out, that I would venture to say that any language not having the `any` type actually actively hates the developer.
[1] https://www.typescriptlang.org/docs/handbook/2/everyday-type...
Re: TypeScript is now officially 10 years old
#46I wouldn't have bet on it.
When it came out alongside Dart, I thought Dart to be the better, cleaner solution. After all, Google created V8.
Microsoft and Hejlsberg didn't seem well suited to tackle something so lightweight as JS. The whole .net suite seemed like an overengineeres mess to me and MS wasn't liked after the IE6 incident.
But on recent years I came to like TypeScript. It really is just JS.
Re: TypeScript is now officially 10 years old
#47And still useless if you are at least half decent in js.
Re: TypeScript is now officially 10 years old
#48I 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 De…
Can be said about regular modern JS as well. Whether your project has types or not is not alone going to determine the success of the project.
Re: TypeScript is now officially 10 years old
#49Any survivors of https://www.typescriptlang.org/docs/handbook/esm-node.html wanna share their experiences?
type module in the package.json, and import every and all .ts file with a .js extension. zero problems for a year or two.
>import every and all .ts file with a .js extension
And recompile on every change, gotcha. I am emphatically not doing either.
EDIT: for future reference, `"type": "module"` is not part of the fix but the thing that opens that particular can of worms. Rotten ones.