Deno will stop using TypeScript
startfunction.com
Deno will stop using TypeScript
1–10 of 359 posts
Re: Deno will stop using TypeScript
#2[deleted]
Re: Deno will stop using TypeScript
#3Thank God, I would really appreciate this. The TypeScript usage was the one thing that I didn't like about Deno.
Why add complexity to a new project which starts from scratch? JavaScript is good enough and there's no need to make it confusing by adding another layer.
Re: Deno will stop using TypeScript
#4Yeah. Same same. Not working, so let’s just fix it by creating another ecosystem instead of fixing compiletimes etc.
I will refuse deno. Too much ego in JavaScript-land. “Everybody wants to be like Mike”. Errr Linus... Lowrey
Re: Deno will stop using TypeScript
#5> While TypeScript is sometimes seen as an improved version of JavaScript, this case is showing that in fact, it’s not.
Woah, woah, hold on. This case is showing that in the very specific, atypical case the Deno team are using it in, TypeScript is not the right fit.
I’d rather read something that actually interviews the Deno folks about what they are doing, the underlying document is a pretty free ranging discussion and this writeup is making a few assumptions.
Re: Deno will stop using TypeScript
#6Thank God, I would really appreciate this. The TypeScript usage was the one thing that I didn't like about Deno. Why add complexity to a new project which starts from scratch? JavaScript is good enough and there's no need to make it confusing by adding another layer.
This is talking about the internal Deno code. The user facing side will still support TypeScript, though you’re also free to not use it if you want.
Re: Deno will stop using TypeScript
#7Thank God, I would really appreciate this. The TypeScript usage was the one thing that I didn't like about Deno. Why add complexity to a new project which starts from scratch? JavaScript is good enough and there's no need to make it confusing by adding another layer.
> JavaScript is good enough and there's no need to make it confusing by adding another layer.
To some people, JS itself is relatively confusing, and TypeScript reduces that confusion.
EDIT: And... someone's clarification is saying this is internal framework code, not userland support for TS. Seems like a non-issue, really. They don't want to use it, but want to provide support for others to use it in their projects.
Re: Deno will stop using TypeScript
#8> It’s worth mentioning that Deno will stop using TypeScript only for the internal Deno code: the Deno user code will still be in TypeScript and thus type checked.
Re: Deno will stop using TypeScript
#9Here's the Deno Design document with the reasoning and some discussion about the decision: https://docs.google.com/document/d/1_WvwHl7BXUPmoiSeD8G83JmS...
This post adds little to what's already said there.
Re: Deno will stop using TypeScript
#10This is gonna be an unpopular opinion but as someone who learned to program in loosely typed languages, I have never seen the TS appeal.
TS feels like something that was created to lure programmers who couldn’t wrap their heads around JS loose nature. Almost like it was created to convince Java and C# developers to use JS.
It have never felt about it like something that would make my code better or more organized. It definitely slows me down with very little benefits in return. (Again, can’t stress enough that this is a personal opinion based on personal use cases)
I appreciate that it forces me to be more intentional about organizing my code but I also get that when I use frameworks.
Of course I also appreciate when I can identify that an error is coming from a type mismatch, but as I said I learned to program in loosely typed languages first, so I never created that concept of defining types in my head. I’m always extra-aware of types mismatches in my JS code and is usually the first thing I check when something goes wrong. But I have never felt the need to have a way to explicitly define the types that I’m working with. I honestly fail to see the benefit when a large amount of code that you have to interact with (libraries and such) was written in classic JS.
Once again. Probably unpopular opinion, so I don’t mind the downvotes.