Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

TypeScript Won

medium.com

Post reply on HN
Print view View original

121–128 of 128 posts

Re: TypeScript Won

#121

Post by SonicSoul »

thejameskyle wrote: post #49

It's frustrating that the only reason thats really given for TypeScript being "better" than Babel is that it has more downloads, using incorrect charts to prove it. Here's the actual download charts if you are interested: https://twitter.com/thejameskyle/status/725344218411986946 Source: - babel-core: http://npm-stat.com/charts.html?package=babel-core&author=&f... - typescript: http://npm-stat.com/charts.html?package…

these are just npm stats. this ignores nuget (visual studio equivalent) and other ways it can be installed including direct download

Re: TypeScript Won

#122

Post by spion »

jkrems wrote: post #72
koolba wrote: post #2

Does anyone here have bad things to say about TypeScript? I haven't used it for any large projects yet (couple toy ones) but seems pretty legit. Based on my anecdata, people who have used it at scale seems to like it. I can't tell if that's because they're still in the honeymoon phase or if it really is a step forward for the long term.

TypeScript's type system is "occasionally typed". E.g. in trivial, C#/Java-style code it works well. And even there it falls back to `any` way too often (and it can become hard to find out way). Flow's type system is designed with modern, more functional style in mind and didn't fail me yet.

Suggestion that solves your problem: don't use TypeScript without "noImplicitAny"

Re: TypeScript Won

#123

Post by d1plo1d »

WorldMaker wrote: post #111
softawre wrote: post #86

Earlier quoted context omitted.

Unions were added in TS 1.4, over a year ago. https://blogs.msdn.microsoft.com/typescript/2015/01/16/annou...

Also, Intersections were added in TS 1.6, last year: https://blogs.msdn.microsoft.com/typescript/2015/09/16/annou... They seem to be moving at a decent, agile pace to improving/expanding upon the algebraic sides of the type system.

Yup, I was definitely wrong on that one. Sorry about that.

Thank you for correcting me.

Re: TypeScript Won

#124

Post by d1plo1d »

mercurial wrote: post #100
Keats wrote: post #93

Earlier quoted context omitted.

The fact that Flow doesn't work on Windows is a big limitation. I prefer the idea of Flow as well but tooling and community is not there yet

There are occasionally Windows builds by the OCamlPro people popping up. The fact that last time I checked, it wasn't able to consume TSD signatures from third-party libraries (or offer an equivalent system with a significant amount of libraries) is a much bigger issue IMHO.

Not terribly related but I am starting to see this as a pattern on the internet:

When I bring up the latest and greatest (eg. Flow) it doesn't actually work on Windows because Windows is as I see it an after-thought for a lot of the Open Source world.

But I've brought up this exact problem (the lag in tooling) to .Net/Windows devs before and they've told me I'm wrong and that they've got all the latest and greatest dev tooling like everyone else.

Re: TypeScript Won

#125

Post by k__ »

spankalee wrote: post #56
jwineman wrote: post #11

Interesting he omits Flow from his very carefully chosen "Typescript won" arguments.

Does anyone actually use Flow? I see TypeScript all over the place.

I do, in production. But yeah, it seems Flow needs more marketing.

TypeScript seems to be rather big for MS. But FB mostly pumps money in Babel and React at the moment...

Re: TypeScript Won

#126

Post by jaredklewis »

chimeracoder wrote: post #63
doodpants wrote: post #53

Earlier quoted context omitted.

I have no experience with TypeScript, but in general the downside of optional language features is when you're working with a team, and different people end up using different dialects of the language.

That doesn't really apply here, because type annotations have no runtime effect. They're effectively comments.

The content of comments isn't enforced by the compiler, so I would say they are not very comment-like.

Re: TypeScript Won

#127

Post by Keats »

Touche wrote: post #90
WorldMaker wrote: post #87

Earlier quoted context omitted.

Pure (vanilla) JavaScript will remain a bit of a rare unicorn in large projects, though, at least until HTTP/2 and maybe even after HTTP/2 for whatever other reasons [1]. Just about every large project has a bundler and/or minifier step and the Typescript transpilation fits right in there, instead of in the browser. [1] People will always still want to shave bandwidth, and the new hotness is Tree Shakers which shave…

Just about every large project has a bundler step for production . Many have for dev as well, but this is unequivocally an undesirable thing. You can't beat Refresh for dev workflows.

I'd say live reload beats refresh for dev workflows (when it works).

Re: TypeScript Won

#128

Post by WorldMaker »

d1plo1d wrote: post #123
WorldMaker wrote: post #111

Earlier quoted context omitted.

Also, Intersections were added in TS 1.6, last year: https://blogs.msdn.microsoft.com/typescript/2015/09/16/annou... They seem to be moving at a decent, agile pace to improving/expanding upon the algebraic sides of the type system.

Yup, I was definitely wrong on that one. Sorry about that. Thank you for correcting me.

Next up on the roadmap, Typescript is working to add opt-in strict null and undefined checking which is probably the last area where Flow's type system is particularly better than Typescript's.

(It will be opt-in as Typescript follows a rule of increasing strictness via compile options to support the spectrum of JS needs, but also as it will not be entirely backward compatible with existing type definition files and will need some effort among typings authors.)

Post reply on HN