3 ms·

uh... people want them because they run into pain points every day, in a project that's actively developing and can solve those pains. Why wouldn't people want

by ajkjk 4y ago

uh... people want them because they run into pain points every day, in a project that's actively developing and can solve those pains. Why wouldn't people want their pain points solved? They're not, like, rare issues. They happen every day, or at least every few weeks. A month can't go by without my putting up a code change that has "unfortunately, TS doesn't support this, so <workaround>" in the description. I love TS but it can certainly be better. edit/afterthought: I just do not care about JS-compatibility per se. It's a nice guideline but I'd like the language I use to be as good as possible, because I'm trying to use it to do things, regardless of their ideology.

wruza 4y ago
Whatever they do, you’ll still have pain points, because people tend to ignore the good and focus on what’s left, and what’s left is never zero for that’s how the universe works. Gods run into pain points all the time. The correct question is not where our pain points are, but how far these pain points are from what we want to do, i.e. are these points a real pain or just our own perfectionist anxiety. Typing for the sake of typing may not help doing the job before thursday.
- ajkjk 4y ago
  Yeah but when you fix this round of pain points and then people complain about the next one... then that means I got a bunch of improvements? Is your point "because you'll still have pain points after improving things, don't improve anything?" that makes no sense. In no sense are the issues with TS "perfectionist anxiety". They're real, fixable problems that make it harder to write safe or simple code.
ptx 4y ago
If you don't care about JS compatibility, that opens up lots of choices. Many languages compile to JS and interoperate without being constrained by syntax-level compatibility. Kotlin [1] is a nice statically typed language, for example. [1] https://kotlinlang.org/docs/js-overview.html https://kotlinlang.org/docs/js-overview.html
- ajkjk 4y ago
  TS is way better than Kotlin, imo. At least last I checked. I mean that I don't care about JS compatibility _exactly_. I still want to write JS, just with all the problems... fixed.

by ajkjk 4y ago

wruza 4y ago

Whatever they do, you’ll still have pain points, because people tend to ignore the good and focus on what’s left, and what’s left is never zero for that’s how the universe works. Gods run into pain points all the time. The correct question is not where our pain points are, but how far these pain points are from what we want to do, i.e. are these points a real pain or just our own perfectionist anxiety. Typing for the sake of typing may not help doing the job before thursday.

ajkjk 4y ago
Yeah but when you fix this round of pain points and then people complain about the next one... then that means I got a bunch of improvements? Is your point "because you'll still have pain points after improving things, don't improve anything?" that makes no sense. In no sense are the issues with TS "perfectionist anxiety". They're real, fixable problems that make it harder to write safe or simple code.

ptx 4y ago

If you don't care about JS compatibility, that opens up lots of choices. Many languages compile to JS and interoperate without being constrained by syntax-level compatibility. Kotlin [1] is a nice statically typed language, for example. [1] https://kotlinlang.org/docs/js-overview.html https://kotlinlang.org/docs/js-overview.html

ajkjk 4y ago
TS is way better than Kotlin, imo. At least last I checked. I mean that I don't care about JS compatibility _exactly_. I still want to write JS, just with all the problems... fixed.