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

31–40 of 88 posts

Re: Turbo 8 is dropping TypeScript

#31

Post by debaserab2 »

tticvs wrote: post #9

> very few programmers are typically interested in having their opinion on typing changed. Most programmers find themselves drawn strongly to typing or not quite early in their career, and then spend the rest of it rationalizing The Correct Choice to themselves and others. He's certainly right about this. I can't wrap my head around why anyone wouldn't want types in their program* The types still exist you just didn'…

I actually don't relate to this statement at all. My college courses were filled with Python, Java, and C#. I loved python. I hated C# and Java even more. I learned PHP in my own free time. I then went on and happily cut my teeth on dynamic languages for the next decade.

I dabbled occasionally with typed languages, but it wasn't until Typescript was forced upon me by a respected coworker that I was able to recognize type safety as a net-win for development speed. Seeing an entire class of problems disappear in a codebase rife with them was an eye opening experience.

I briefly took a ruby job a little over a year ago and I missed type safety quickly. Despite how much I love Ruby, I love tracing through code paths to understand what a variable is a lot less.

Re: Turbo 8 is dropping TypeScript

#32

Post by claytongulick »

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.

Probably true. After 30 years of writing code, I guess I just haven't figured it out yet.

Thankfully you and Typescript are here to show me how to do it right.

Re: Turbo 8 is dropping TypeScript

#33

Post by bottlepalm »

claytongulick wrote: post #32
bottlepalm wrote: post #17

Earlier quoted context omitted.

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

Probably true. After 30 years of writing code, I guess I just haven't figured it out yet. Thankfully you and Typescript are here to show me how to do it right.

What languages have you written for 30 years? and what about TypeScript is so challenging for you? Especially if you’ve already spent time with other statically typed languages.

Re: Turbo 8 is dropping TypeScript

#34

Post by claytongulick »

bottlepalm wrote: post #19
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)

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.

Re: Turbo 8 is dropping TypeScript

#35

Post by hinell »

quickthrower2 wrote: post #27
coel wrote: post #26

Earlier quoted context omitted.

With ts-node or Deno there is no compile step you have to do yourself. For frontend, bundlers can be setup where it is pretty transparent.

I have found practically with ts-node or bundlers ... you can get knocked off the happy path, have problems, you need to fiddle with tsconfig.json and you need to spend ages in StackOverflow posts to fix it. This sometimes happen if you want to use a certain library, or doing a mass upgrade of a 2 year old project. I have no experience with Deno.

This. Pseudo-runtimes can't guarantee anything.

Re: Turbo 8 is dropping TypeScript

#36

Post by hinell »

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…

It's not a Type System denouncement, it's denouncement of crappy TS and that's the right choice.

Re: Turbo 8 is dropping TypeScript

#37

Post by bottlepalm »

claytongulick wrote: post #34
bottlepalm wrote: post #19

Earlier quoted context omitted.

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…

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.

Re: Turbo 8 is dropping TypeScript

#40

Post by LudwigNagasena »

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.

Post reply on HN