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

51–60 of 88 posts

Re: Turbo 8 is dropping TypeScript

#51

Post by muxr »

LudwigNagasena wrote: post #40
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…

> 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.

Re: Turbo 8 is dropping TypeScript

#53

Post by didntcheck »

bottlepalm wrote: post #17
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…

I often wonder if people who have trouble typing things, or have to us the 'any' type, ever really learned how to program.

Yep, when I hear people say things like "I like $dynamic_language because I don't have to think about what types I'm supposed to put when I write my functions" or similar, I'm just thinking "how the hell can you write a function without knowing what types you want to receive and return?". I do love the "productivity benefits" of having to read entire function bodies to reverse-engineer what types I'm supposed to pass, because the docstring just used vague terms like "file" or "user"

Re: Turbo 8 is dropping TypeScript

#54

Post by ezekg »

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.

Re: Turbo 8 is dropping TypeScript

#55

Post by DojoAsh »

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 someone* to get around typing. Like, "I love building enterprise systems in C++, but I just really miss all those runtime errors that could/should have been caught by the complier."

So maybe the trajectory of languages gives a clue as to which is better.

*I know that would be incredibly difficult, but we programmers are a resourceful bunch.

Re: Turbo 8 is dropping TypeScript

#57

Post by __loam »

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.

Re: Turbo 8 is dropping TypeScript

#59

Post by coderhs »

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 rationalizing The Correct Choice to themselves and others.

Post reply on HN