Live data from Hacker News

TypeScript Won

medium.com

71–80 of 128 posts

Re: TypeScript Won

#71
Weird comparisons. People who like Elm aren't going to switch to TypeScript because it's more popular. They are fundamental disagreements that can't be dismissed with a Google Trend chart.

TypeScript is currently popular but popularity in JavaScript never last long. The cycle is:

* A library that comes out that solves a problem with the previous iteration.

* The new popular library has some different problem but people ignore it because the new cool thing is still fresh in their minds.

* People become annoyed with the popular library and someone makes a new library that fixes the problem with the popular library. It looks a lot like the original library that popular library replaced.

* Cycle repeats itself.

Re: TypeScript Won

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

Re: TypeScript Won

#73

I could quibble with the conflation of correlation w/ causation for a lot of the comments this post makes about es6/babel or coffeescript. But each time i re-read this post, the cohesive point that pops out most is that this post is basically a Donald Trump speech about Typescript. The claim is that it's bigger, it's better, and everyone else is a bit sad. It disingenuously claims that it's not about about competitio…

I can't think of any downsides of an optional type checker. Can you? Just curious if there's an argument I hadn't heard before.

Re: TypeScript Won

#74
Choosing a winner based on Google Trends?

Hmm.

Pointing out that CoffeeScript is on the decline because Google Trends for it once peaked and has since declined?

Hmm.

Failing to consider that TypeScript might be at a similar peak and is due a similar decline?

Hmm.

Re: TypeScript Won

#75
post #67

Earlier quoted context omitted.

I've given up on trying to have serious discussions about these things on Hacker News. It's a really bad community for that sort of thing. Find me elsewhere if you want to have that discussion.

Ever wondered if it's exactly because of people discussing like this?

I don't particularly care what it is. This is the discussion forum where I've been told that Babel single-handedly has "destroyed the web platform" and all sorts of just senseless attacks, including ones that get way too personal.

No, if this community wants to act like a bunch of 12 year olds then that is their prerogative, but I'm not going to be part of it.

Again, I'm more than happy to talk about this anywhere else.

Re: TypeScript Won

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

Like other compile-to-JS languages such as coffeescript, I don't think it has enough to offer over plain JS to justify its existence. Coffeescript was great because it drove a bunch of language features into consideration for ES6, but actually writing in it seemed like more pain than it was worth. Consider being in the situation of being in charge of a large coffeescript codebase, today. No thank you.

Funny, I feel the exact opposite about CoffeeScript, but maybe I'm not using enough advanced features.

In particular I like how readable and clean CoffeeScript is when you have a long series of callbacks.

Re: TypeScript Won

#77

I could quibble with the conflation of correlation w/ causation for a lot of the comments this post makes about es6/babel or coffeescript. But each time i re-read this post, the cohesive point that pops out most is that this post is basically a Donald Trump speech about Typescript. The claim is that it's bigger, it's better, and everyone else is a bit sad. It disingenuously claims that it's not about about competitio…

But that's kind of what the article is about, isn't it? TypeScript is a way of having types and yet existing in a typeless world.

Re: TypeScript Won

#78
post #26

Is Typescript/Babel an either/or choice? ES6 is non-negotiable. I understand the basic premise behind Typescript. Would I "switch" from Babel to Typescript and get arrow functions and string interpolation through Typescript somehow?

Yes, because Typescripts is 2 things: * A language, superset of ES6 that adds optional types * A compiler (like Babel) that will take your Typescript code, check if the types are correct, remove them, and transpile the non-ES5 parts of into ES5 (just like Babel). So if you want to use Typescript-the-langage, you need Typescript-the-compiler and you will no longer need Babel.

Many people choose to use both. TypeScript for type-checking and stripping types, and Babel for compiling down ES2015 code. Babel follows the spec for that much closer than TypeScript does and has hundreds of plugins that allow you to do even more.

Re: TypeScript Won

#79
post #73

I could quibble with the conflation of correlation w/ causation for a lot of the comments this post makes about es6/babel or coffeescript. But each time i re-read this post, the cohesive point that pops out most is that this post is basically a Donald Trump speech about Typescript. The claim is that it's bigger, it's better, and everyone else is a bit sad. It disingenuously claims that it's not about about competitio…

I can't think of any downsides of an optional type checker. Can you? Just curious if there's an argument I hadn't heard before.

If it's TypeScript versus pure JavaScript (not versus Babel), there's a transpile time hit you must consider.

Re: TypeScript Won

#80
post #67

Earlier quoted context omitted.

Ever wondered if it's exactly because of people discussing like this?

I don't particularly care what it is. This is the discussion forum where I've been told that Babel single-handedly has "destroyed the web platform" and all sorts of just senseless attacks, including ones that get way too personal. No, if this community wants to act like a bunch of 12 year olds then that is their prerogative, but I'm not going to be part of it. Again, I'm more than happy to talk about this anywhere el…

So you're taking your ball and going home? LOL. Nana nana boo boo!
Post reply on HN