Hacker News Reader

Comment by snek | Hacker News Reader

Gotta appreciate the part implying that anyone who finds this document amusing is a "novice" programmer.

I thought the "novice" programmer remark was a pretty cringe-worthy comment.

The original reasons listed by Deno for removing TS had the undertones of "senior engineer who hates certain tech because they didn't use it right". Naturally, their response was to say "you probably don't understand cause you're a novice".

I can sympathize with their issues. TS compiles are slow as fuck, and if I could find anything that was just as nice without the long compiles I’d switch in a heartbeat.

But I don’t think I’d ever want to go back to plain Javascript.

My sentiment as well.

There are efforts to provide faster compilation times: - https://github.com/evanw/esbuild - awesome, I use it for most of my ts projects - https://swc-project.github.io/ - also awesome, but has some bugs

Esbuild is cool, but if it doesn’t check the types then using Typescript is a bit pointless in the first place.

Guess a combination of esbuild during development, and tsc during commit would be the best of both worlds.

Not necessarily, TS issues are found in the editor which is where most of the use is. I don't test types only on compile but usually through VSCode itself.

Thumbs up for esbuild, it's awesome.

That passage didn't say anything about finding the document 'amusing'.

Reply on news.ycombinator.com