[cambalache]

I like Javascript and Express, so in that sense they are OK. I hate the brittleness of the ecosystem, the "flavor of the month" character, and the explosion of options, there are people who like that setup: small programs that you can plug and play to create your whole stack, I find that tiresome, I prefer big monoliths in which the best options and practices are universally agreed upon.

Ah and I hate Typescript, nice idea, but when you spend 30% of your time looking after all those custom types and end up using an ":any" hack to make it work, this leaves a bad taste in your mouth. If I am going to use strong types I would choose an actual strongly-typed language for that, C# is great.

[halfmatthalfcat]

Somewhat ironic but not sure if you know, Typescript is made by Microsoft and the lead Typescript language architect is Anders Hejlsberg who also was heavily involved in the creation and architecture of C#.

[AlchemistCamp]

There's no irony in finding limitations when building on a poorly planned foundation that don't exist when starting from a clean slate.

[cambalache]

Exactly, the idea is great and you can clearly notice the intention of making JS more C#-like, but the foundation is not suitable. Could you imagine trying to "C++size" the whole Python ecosystem? Shudders!

BTW dude I like your content, after Rails, Phoenix is my preferred stack, so nice, and the community is cool, too bad the job opportunities are not there yet in sufficient quantities.

[mekster]

If you have to end up using "any" on something not too weird, then you probably aren't getting TypeScript right.

The typing system is way better than php, ruby or swift I feel like I'm using a language of a generation behind after using TypeScript.

[411111111111111]

good thing he didnt think of phps, ruby nor swifts typing system then.

he made a specific example and it holds true. languages like c# and java are just better at it and typescript is kinda in between. not great, but maybe good enough for a lot of people.