The tragedy of running an old Node project

Re:The tragedy of running an old Node project by cies on Wednesday November 20, 2024 @07:19PM (#42199653)

JS is popular due to it being the only browser lang. Did you forget that?

Also: TS popularity shows that not everyone in the JS community agree with you.

For server side web dev you will find that statically typed langs (Java, Kotlin, C#, Go) are a big chunk of the pie. Sure it also comes down to taste, but if you work in a large team, having stronger types can greatly help to keep the codebase in shape. (better IDE refactor tools, clearer for noob, harder to hide/ check in rubbish to git)

If you are afraid by obscurity, have a look at Kotlin!

[ Parent | on HN ]

Re:The tragedy of running an old Node project by leptons on Thursday November 21, 2024 @03:57AM (#42202391)

Typescript is still nowhere near as popular as Javascript, and likely never will be. It's overkill for the vast number of uses of Javascript.

[ Parent | on HN ]

Re:The tragedy of running an old Node project by cies on Thursday November 21, 2024 @08:43AM (#42204216)

JS's uses have been growing steadily. The language was clearly not "designed" (I saw a talk about the first 10d of JS, little actual designing happened).

TS is to the rescue when you have a big JS project, because that's what JS is not good at: big projects and large teams.

[ Parent | on HN ]

Re:The tragedy of running an old Node project by phatskat on Thursday November 21, 2024 @07:37PM (#42210150)

I’d love a link to this talk if you happen to have it handy!

[ Parent | on HN ]

Re:The tragedy of running an old Node project by leptons on Thursday November 21, 2024 @11:50PM (#42211295)

Except big JS projects with large teams existed well before Typescript ever did, and it never stopped anyone from producing good results. Typescript really isn't making anything possible that wasn't possible before Typescript existed.

[ Parent | on HN ]