this post was submitted on 10 Sep 2023
113 points (98.3% liked)
Out of the loop
10958 readers
2 users here now
A community that helps people stay up to date with things going on.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm not really involved in javascript land so im parroting off of what i've heard for "why js over ts?"
So mainly: devs who don't prefer strongly typed languages, and library devs who find typescript to be less transparent and more time consuming for new and old contributors than it's worth
Not a bad summary, but I take issue with all the points
Edit: The sourcemap comment is relevant to package size and not to final bundle size per the HN comment linked below. Also, the cmd+click critique rings truer now that I know it's in the context of an installed package. Another critique is build time which is fair enough.
I understand why some hobbyist individuals with small-ish scripts might not see the value, even though I even still disagree there.
The more code and people touching the code, the more value you'll see.
Hell I even write my tiny userscripts in TS and compile it to JS. The editor/"intellisense" support is nice
Thanks :) I didn't see anyone mention the points made by the svelte guys https://news.ycombinator.com/item?id=35892250 which is a shame since I thought they made better points than the dramatic "type gymnastics" argument haha (i am biased toward type-safety, as long as there is idiomatic, algebraic data types w/ pattern matching)
Overall it sounds like a major change with a few minor/moderate benefits, but it's their choice and time will tell if it was worth it :P