Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Turbo 8 is dropping TypeScript

world.hey.com

Post reply on HN
Print view View original

81–88 of 88 posts

Re: Turbo 8 is dropping TypeScript

#81

Post by etler »

quickthrower2 wrote: post #22

So I have been musing on TS this for a while. I put my self in the rare “open minded about types” camp. My biggest beef with TS is you need to compile it, and JS development has enough complexity with module systems and stuff as it is. Compile to JS languages IMO should take the entire burden away like Elm does, otherwise they add a lot of troubleshooting work. I wonder if type annotations on plain JS could be the wa…

Are you doing full stack or backend development? On the browser a build step is needed anyways as you need transpilation to be able to use new ecmascript features, and you need a bundler for module management. Node is kept more up to date so I can see skipping compilation for that. I was already used to needing a build step before switching to typescript so it didn't matter much to me.

Re: Turbo 8 is dropping TypeScript

#82

Post by etler »

AirMax98 wrote: post #11

As someone who regularly writes both JS and TS, I'm fairly certain that this dichotomy is not real. There are places where TS makes more sense (eg large, trustless applications with many devs) and places where JS makes more sense (eg libraries that would otherwise need to have very abstract types). I'd understand opting for either JS or TS as a policy going forward, but it's hilarious that this dude probably worked h…

I don't think the dichotomy exists because the TS ecosystem is autonomous. You can use TS with any JS library through type declarations and the definitely typed repo. What the js community thinks about typescript honestly doesn't matter. The only practical difference it makes for me is having to do `npm add @types/{library_name} -D`

Re: Turbo 8 is dropping TypeScript

#83

Post by PH95VuimJjqBqy »

andkenneth wrote: post #28
quickthrower2 wrote: post #22

So I have been musing on TS this for a while. I put my self in the rare “open minded about types” camp. My biggest beef with TS is you need to compile it, and JS development has enough complexity with module systems and stuff as it is. Compile to JS languages IMO should take the entire burden away like Elm does, otherwise they add a lot of troubleshooting work. I wonder if type annotations on plain JS could be the wa…

He basically had this option, and it's the way that Rich Harris and the Svelte team went a few months back by adopting JSDoc, and honestly his reasoning for dropping typescript in favor of another typing system is pretty sound and did result in clear benefits for both users and maintainers. DHH has something specific against types in general which I really don't understand. And that's fine, I'm happy to let him and 3…

Nothing is stopping people from using JSDoc, your arguments here don't make any sense.

Re: Turbo 8 is dropping TypeScript

#84

Post by PH95VuimJjqBqy »

seattle_spring wrote: post #67
muxr wrote: post #51

Earlier quoted context omitted.

libraries if they are popular in general are expected to work with a wide variety of code. Supporting code smell is a feature.

Can you share some examples of libraries you feel benefit from this sort of unlimited flexibility?

jquery

Re: Turbo 8 is dropping TypeScript

#85

Post by sngz »

bil7 wrote: post #3

My 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…

sounds like a user problem

Re: Turbo 8 is dropping TypeScript

#86

Post by sngz »

etler wrote: post #79
bil7 wrote: post #3

My 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…

The benefits of typescript when refactoring is immense. I have a really hard time understanding how someone could not see the net productivity gain if they've experienced refactoring in typescript vs JavaScript.

> I have a really hard time understanding how someone could not see the net productivity gain if they've experienced refactoring in typescript vs JavaScript.

cause I spend more time debugging other peoples typescript code that is usually a typescript problem and is obfuscated by the extra layer. If we used vanillaJS then it would save everyone so much time.

Re: Turbo 8 is dropping TypeScript

#87

Post by sngz »

thomasfromcdnjs wrote: post #8

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)

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

Re: Turbo 8 is dropping TypeScript

#88

Post by hbrn »

DojoAsh wrote: post #55

Typescript solved the "I spent hours debugging, only to find I misspelled a property" problem. FastAPI did the same for Python. I have noticed that untyped languages (or "dynamic" languages, if that makes it sound more advanced) have typing added to them by people who love the language, but hate 10x debugging. On the other hand, I can't think of a single example of a strongly typed language that has been "fixed" by s…

> I can't think of a single example of a strongly typed language that has been "fixed" by someone* to get around typing

Dependency injection is exactly that.

Post reply on HN