← Back to context

Comment by thomasfromcdnjs

2 years ago

I've been writing Javascript for 20 years.

Typescript has done nothing for me.

Just a religious battle at this point.

(I'm okay with it on the server, but client side is just something something)

I would love to see the flawless code you've written over 20 years where static typing would have done nothing for you or anyone else maintaining your code.

  • You sure do seem to have it in for folks who don't share your opinion. You've been pretty aggressively posting all over this discussion.

    No one is trying to kill your puppy or taking your types away.

    Competent people can have different opinions.

    You have something that works for you. Great.

    The fact that you don't understand why others don't share your opinion doesn't make them wrong or "incompetent" as you said in a different comment.

    • Have an actual argument? Hopefully a better one than DHH’s, “it’s too hard to type things” Like how bad of a programmer do you need to be? It’s ok to call people out even if they’re popular. Like all the commenters on his PR.

    • > No one is trying to kill your puppy or taking your types away.

      dhh literally took people’s types away. People don’t like that.

> I'm okay with it on the server

I used to be pretty religious about it NOT being on the server, but nowadays I just say to myself: Who am I to say JavaScript can't be used on the server?

What about PHP on the client side? Why is suddenly Python a server-side language when it's a scripting language better suited for data analysis and manipulation? WASM? Is not ASM an applications language instead?

This line of thinking broke me of these thought-limiting shackles, and now I think: If there's a toolchain to make it run on your target (client side browser, server side app, at your OS as a service script, embedded devices, whatever), then go for it.

typescript has wasted more of my time than anything else. But at least I can bill clients for it.