I'd understand opting for either JS or TS as a policy going forward, but it's hilarious that this dude probably worked himself up so intensely about this that he brazenly rug-pulled his own repo and invalidated all open PRs.
Turbo 8 is dropping TypeScript
11–20 of 88 posts
Re: Turbo 8 is dropping TypeScript
#12Strong-typed languages can be a source of burn and frustration if you're not used to them, especially when starting your programming career (and I sense DHH comes from this standpoint on his last paragraph there).
I know many programmers that have chosen weakly-typed languages because they found it simpler, faster time-to-HelloWorld-success, rather than fighting the compiler for cryptic compiler and linking errors. I was burned like this when I first found C++ and Delphi back when I was 12 years old.
I consider strong-typing beautiful for two reasons:
- You get to be explicit on how you want the bits you're handling being interpreted. Some languages will even let you write your own typecasting functions and comparison operators, further extending the language capabilities (though they may tend to be more verbose).
- It helps code analyzers do their job, helping you to avoid a shoot in the foot (IntelliSense, IDEs with similar technologies).
In my argument I'm abiding to the "explicit is better than implicit" principle which is not only a Zen of Python thing; every programming language benefits from this approach (more control, more readability, explicit intention, less uncertainty).
Re: Turbo 8 is dropping TypeScript
#13Some further discussion to be had on the corresponding GitHub pull request: https://github.com/hotwired/turbo/pull/971
Re: Turbo 8 is dropping TypeScript
#14I'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 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.
Re: Turbo 8 is dropping TypeScript
#15This seems like a step in the wrong direction.
Re: Turbo 8 is dropping TypeScript
#16Re: Turbo 8 is dropping TypeScript
#17My least favourite thing about vanilla JS is finding out at runtime that I made a typo. That's an annoying thing that TS completely solves, among many others. I really don't see how you could use TS for any amount of time and wish to revert back. >Things that should be easy become hard, and things that are hard become `any`. No thanks! Denouncing a type system because you refuse to use it correctly seems short sighte…
Re: Turbo 8 is dropping TypeScript
#18> ...very few programmers are typically interested in having their opinion on typing changed. > Free of strong typing. Strong-typed languages can be a source of burn and frustration if you're not used to them, especially when starting your programming career (and I sense DHH comes from this standpoint on his last paragraph there). I know many programmers that have chosen weakly-typed languages because they found it s…
Re: Turbo 8 is dropping TypeScript
#19I'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)