Live data from Hacker News

Announcing TypeScript 1.7

blogs.msdn.com

91–93 of 93 posts

Re: Announcing TypeScript 1.7

#91
post #88

Earlier quoted context omitted.

>This is Incorrect, it doesn't assume anything. Dart's method cascades just returns the receiver, it doesn't matter what the method returns, it's value is ignored and receiver is returned instead. ... which would only be useful if the method was void-returning or returned the this-instance, i.e., it didn't return a new instance and left the LHS unmodified.

> which would only be useful if the method was void-returning or returned the this-instance Simply untrue, there are plenty of times methods have side-effects that return something other than void or itself, e.g: - Incrementing a value and returning the current value - Inserting or Updating rows and returning the number of rows affected - Setting an entry and returning whether there was an existing entry or not

The example I was responding to was about "setupBase" and "setupAdvanced"...

Re: Announcing TypeScript 1.7

#92

I'd like to see a thorough comparison of typescript, haxe, scala.js, and also gopherjs. Which (statically typed) language/compiler provides the best experience for developers who want to develop "native" programs (I include here jvm and node) and javascript for the web with one language using the same libraries?

http://www.scala-js.org/ has a nice comparison between JavaScript, ECMAScript 6, TypeScript and Scala. I'm not sure there is much substance to develop "native" programs in TypeScript/Haxe/... they don't have an ecosystem outside the web, while Scala has tons of mature libraries, access to all the Java stuff ever written, and runs on the best, mature, well-supported, high-performance runtime you can get.

ts has the node ecosystem, and haxe provides easy access to node/pyton/c++/java libs. gopherjs is able to compile a significant amount of the go standard lib -- I don't know if this is true for arbitrary go libs too.

Thanks for the reference.

Re: Announcing TypeScript 1.7

#93
post #64

Earlier quoted context omitted.

There are some subtle behavioural differences between the Language Service and the regular compiler, for example: https://github.com/Microsoft/TypeScript/issues/5243

Good clarification. Perhaps the compiler API is the better choice here? I'm not fully aware of the differences / divisions between the two. https://github.com/Microsoft/TypeScript/wiki/Using-the-Compi...

Interesting, I honestly don't know if that makes a difference.
Post reply on HN