Live data from Hacker News

Deno will stop using TypeScript

startfunction.com

11–20 of 359 posts

Re: Deno will stop using TypeScript

#11
post #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…

Lawd, the number of times people write an extensive essay detailing how a particular tool didn’t fit their culture, processes, and circumstances, then explain why it’s either irredeemably broken or conversely, that failing to adopt the tool is professional malpractice.

N=1. That is all.

Re: Deno will stop using TypeScript

#12

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

[deleted]

Re: Deno will stop using TypeScript

#13
They should just use deno to run their setup, there would be no compilation if they did that. ;)

Someone is trying to rewrite tsc in rust for speed up here - https://github.com/swc-project/swc

Cool project for runtime checking with ts - https://github.com/gcanti/io-ts

Edit: Remove unmaintained runtime type checking library.

Re: Deno will stop using TypeScript

#14
Why such a large, important project would want to drop static types is beyond me.

> TypeScript isn’t proving itself helpful to organize Deno code. On the contrary, the Deno team is experiencing the opposite effect. One of the issues mentioned is that they ended up with duplicate independent Body classes in two locations

This feels like process immaturity or unfamiliarity. Thousands of other projects manage to do just fine.

These folks are free to do what they want with their project, but this is not a good look, especially to those that are skeptical of the javascript ecosystem.

Re: Deno will stop using TypeScript

#15

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

You don’t see the benefits of a strongly typed language?

Re: Deno will stop using TypeScript

#16
post #14

Why such a large, important project would want to drop static types is beyond me. > TypeScript isn’t proving itself helpful to organize Deno code. On the contrary, the Deno team is experiencing the opposite effect. One of the issues mentioned is that they ended up with duplicate independent Body classes in two locations This feels like process immaturity or unfamiliarity. Thousands of other projects manage to do just…

Lisp is large, important, and also not statically typed. It's worked out ok for Lisp programmers. JS itself isn't strongly typed and is the most successful and important language in the world (probably in the history of programming), so that's two game-changers that don't require static typing.

Re: Deno will stop using TypeScript

#17

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

Deno is made by the guy who made Node. So no change in notoriety there.

Re: Deno will stop using TypeScript

#19
post #16
post #14

Why such a large, important project would want to drop static types is beyond me. > TypeScript isn’t proving itself helpful to organize Deno code. On the contrary, the Deno team is experiencing the opposite effect. One of the issues mentioned is that they ended up with duplicate independent Body classes in two locations This feels like process immaturity or unfamiliarity. Thousands of other projects manage to do just…

Lisp is large, important, and also not statically typed. It's worked out ok for Lisp programmers. JS itself isn't strongly typed and is the most successful and important language in the world (probably in the history of programming), so that's two game-changers that don't require static typing.

there's plenty of huge software projects in dynamically typed languages.

There are also huge classes of bugs that exist in these projects that a statically typed language completely eliminates!

If they're running into trouble from having to have types, it's almost certainly design and architecture issue and does not make me think that deno is going to be a solid project.

Re: Deno will stop using TypeScript

#20

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

You don’t see the benefits of a strongly typed language?

Python is strongly typed, don't confuse static and strong typing.
Post reply on HN