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

41–50 of 128 posts

Re: TypeScript Won

#41

Post by akavi »

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.

The ability to programmatically generate methods/classes can be really powerful and, as far as I can tell, impossible with Typescript (and most statically typed languages).

Back in my Backbone + CoffeeScript days, I reimplemented Rails style has_many/belongs_to "class methods" on Backbone.Model, and it was incredibly useful. But would've been doubly so if I could have had it statically checked somehow.

Re: TypeScript Won

#43

Post by hiou »

If you like typescript so much you might as well stop pretending you write JavaScript and just write in C# like you really want to.

http://bridge.net

If typescript was simply type safety that would be one thing. It's definitely a lot, lot more than that.

Typescript is to .NET as Coffeescript was to Ruby. A bunch of developers who didn't know JavaScript and wanted to find the closest thing they could to what they already knew. And who really uses Coffeescript anymore? Stick with esnext to babel and the bright future JavaScript has ahead.

Re: TypeScript Won

#45

Post by mordocai »

knowtheory wrote: post #21

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…

On point 2, I don't think an optional type checker has any real downsides that I can think of (optional because with typescript you don't have to add type annotations to your code). It helps with debugging and possibly performance but you can choose not to use it.

The rest of your comment I agree with.

Re: TypeScript Won

#46

Post by coroutines »

hiou wrote: post #43

If you like typescript so much you might as well stop pretending you write JavaScript and just write in C# like you really want to. http://bridge.net If typescript was simply type safety that would be one thing. It's definitely a lot, lot more than that. Typescript is to .NET as Coffeescript was to Ruby. A bunch of developers who didn't know JavaScript and wanted to find the closest thing they could to what they alre…

I say again: Javascript can learn many things more from Coffeescript.

Coffeescript's future is diminished, presently (hah) - but ES6 only picked up a handful of magical features.

Re: TypeScript Won

#47

Post by mordocai »

akavi wrote: post #41
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.

The ability to programmatically generate methods/classes can be really powerful and, as far as I can tell, impossible with Typescript (and most statically typed languages). Back in my Backbone + CoffeeScript days, I reimplemented Rails style has_many/belongs_to "class methods" on Backbone.Model, and it was incredibly useful. But would've been doubly so if I could have had it statically checked somehow.

I don't know if it is possible in any practically used statically typed languages, but I can think of nothing that would prevent you from doing metaprogramming in a statically typed language on a theoretical basis. It might be a bit hard to implement, but I think it should be perfectly possible.

Re: TypeScript Won

#48

Post by LukeB_UK »

pjmlp wrote: post #33
symlinkk wrote: post #24

I bet we'll be seeing a lot more of Typescript in the next few years, seeing as it's the default language that is suggested in Angular 2's documentation. I find it odd that Dart wasn't the default language of choice for Angular 2 (although it is fully supported) seeing as Google is behind both projects. I think it really boils down to what the author wrote here: "Dart is not JavaScript. TypeScript is." At the end of…

For me it was a clear message to the outside world, how little backing Dart has inside Google, if their management allows for choosing a programming language designed by the competition instead of their own one, for their own products.

Or it shows that they see that there's already an established base of people using TypeScript, more than Dart, and choosing to follow where the community exists. Throughout the development of Angular 2 the team also talked with the developers of other frameworks, libraries and tools, which shows that they believe in the community more than trying to push their own agenda.

Re: TypeScript Won

#49

Post by thejameskyle »

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=typescript&author=&f...

Also if you want types with Babel, use Flow– which is arguably a much better type system anyways.

Re: TypeScript Won

#50

Post by spankalee »

pjmlp wrote: post #33
symlinkk wrote: post #24

I bet we'll be seeing a lot more of Typescript in the next few years, seeing as it's the default language that is suggested in Angular 2's documentation. I find it odd that Dart wasn't the default language of choice for Angular 2 (although it is fully supported) seeing as Google is behind both projects. I think it really boils down to what the author wrote here: "Dart is not JavaScript. TypeScript is." At the end of…

For me it was a clear message to the outside world, how little backing Dart has inside Google, if their management allows for choosing a programming language designed by the competition instead of their own one, for their own products.

You saw "allowed" like it's a bad or unusual thing. Allowing is the way Google works.
Post reply on HN