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

61–70 of 88 posts

Re: Turbo 8 is dropping TypeScript

#61

Post by eterevsky »

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'm not sure about "spending hours". In my experience it's more like "detect an error during compilation instead of an exception during execution". Once you see the exception, it's usually quite clear what exact property is misspelled. So strong typing saves a few second of execution and reduces the need for some types of unit tests.

Re: Turbo 8 is dropping TypeScript

#63

Post by Destiner »

muxr wrote: post #51
LudwigNagasena wrote: post #40

Earlier quoted context omitted.

> places where JS makes more sense (eg libraries that would otherwise need to have very abstract types) If your library is hard to type, it is a code smell. In my opinion, such libraries could benefit from TS a lot.

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

variety of code is one thing, your library can be used in thousands of places, doesn't mean it have to do thousands of different things

Re: Turbo 8 is dropping TypeScript

#64

Post by Destiner »

LudwigNagasena wrote: post #39
lynxerious wrote: post #38

they removed prettier in the codebase too, they really don't like formatting or typings in their codes.

No reason to use prettier if you already use eslint. And there is no reason to not use eslint, so…

not really, those tools somewhat overlap, but they have completely different purposes (formatting vs linting)

Re: Turbo 8 is dropping TypeScript

#65

Post by qwoter »

coderhs wrote: post #59

sarcasm They should also remove tests from the projects as well. Such a burden on the developer to write test and worry about how to test when they just need to focus on implementing the logic. Very few programmers are typically interested in having their opinion on writing test changed. Most programmers find themselves drawn strongly to testing or not quite early in their career, and then spend the rest of it ration…

Tests are literally type replacement in dynamic languages, only controlled. It's always mentally easier to do what you are forced to instead of writing tests consciously. That is how the other side is looking at people who tell everyone that there is no coding without typing. People who surrender "think more, do less", instead doing more and thinking less - More is less sounds disgusting to me.

A big part of development is prototyping, it sucks so much to use a language that doesn't support efficient prototyping. And no, jumping from Typescript concepts/style to pure Javascript is not an efficient solution, you have limited space in your brain.

I can continue, literally all Typescript code is horrible legacy in the making. In the future people would hate it is so much that comments like this would look ridiculous, remember my words.

Re: Turbo 8 is dropping TypeScript

#67

Post by seattle_spring »

muxr wrote: post #51
LudwigNagasena wrote: post #40

Earlier quoted context omitted.

> places where JS makes more sense (eg libraries that would otherwise need to have very abstract types) If your library is hard to type, it is a code smell. In my opinion, such libraries could benefit from TS a lot.

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?

Re: Turbo 8 is dropping TypeScript

#68

Post by seattle_spring »

LudwigNagasena wrote: post #39
lynxerious wrote: post #38

they removed prettier in the codebase too, they really don't like formatting or typings in their codes.

No reason to use prettier if you already use eslint. And there is no reason to not use eslint, so…

I recommend reading up on what Prettier does, because you can and should be using both.

Re: Turbo 8 is dropping TypeScript

#69

Post by ezekg »

__loam wrote: post #57
ezekg wrote: post #54

Instead of acting like children, bullying/attacking others, and opening up bogus PRs, maybe those people should invest that effort into a @types/turbo package. Wouldn't take more than an afternoon to pull in the old types and call it a day.

I mean this guy unilaterally moved the whole repo off of typescript in the span of 3 hours because of some personal opinions he had. If anyone is acting like a child, it's dhh himself.

I don't think that's an entirely accurate portrayal of the situation. His team has, AFIAK, removed the compilation step from their workflow (or are trying to), deciding to ship unadulterated ES6 to the browser, so they 1) removed TypeScript, and 2) removed Prettier. Both of these require a build/compilation step, which they're moving away from. That's literally it.

The Turbo library is not consumed like a normal package anyways, so these types were only used internally. Nobody relies on these types.

It's their library. And others have done the same recently.

Post reply on HN