Announcing TypeScript 3.0 RC

https://blogs.msdn.microsoft.com/typescript/2018/07/12/announcing-typescript-3-0-rc/

49 12 8 years ago

blogs.msdn.microsoft.com

sbjs3• 8 years ago

This is really exciting! I actually ran into two problems that this already solves, one of which I briefly touched on in the article I posted to HN this morning.

One is project structure. I came up with a solution for type-safe RPC that required a shared file for type definitions, and my solution was to symlink that file. It looks like the new project feature should let me get rid of that and have a "shared" TS project as a sibling to "server" and "client"!

The other is spread arguments. I recently ran into the error "Spread types may only be created from object types" [1] and I think this feature is addressed by TS 3.0!

[1] https://github.com/Microsoft/TypeScript/issues/13557

Call me crazy, but I really think TypeScript is the future of the web and I'm betting my whole career on it by diving deep into it and becoming an expert on it so that I can do consulting as a TypeScript & React expert.

smt883• 8 years ago

I love TS but don't see it as the future of the web. It's currently the best way to write JS and use the JS/Node ecosystems, but compile-[insert better language here]-to-wasm will be more compelling than TS in the future.

sbjs3• 8 years ago

I don't think wasm and JS are competitors. From what I can tell, wasm currently isn't blessed with the same first-class citizenship in the browser that JS is, and I don't think that's in the works either. It looks like wasm is mainly meant for porting C libraries to the browser (Emscripten style) and maybe the occasional Doom or Quake just because.

Stoids• 8 years ago

Does this release actually fix the generic spread type issue? I believe that issue is being worked on elsewhere [1]. Would love to be wrong though because that error is quite annoying.

Still a really strong release though. The tuple changes are going to cut down an insane amount of overloads that I currently have to write myself (while maintaining the arms race of "just one more overload"). The unknown type is wonderful for a strict alternative to any--will be super useful at the seams of your app.

[1] https://github.com/Microsoft/TypeScript/pull/13288

nojvek2• 8 years ago

Typescript is definitely great and brings a lot of new ideas to type systems. I really wish python had such great tooling. Mypy leaves a lot to be desired.

nojvek2• 8 years ago

Typescript magic build stuff is useful. Although a realization needs to be made that webpack is the king of front end build systems. Mostly because it’s able to package all sorts of things into a single js/css file.

So any speedups in wbepack with Typescript would be very much appreciated by the community.

syspec• 8 years ago

webpack is king, but ill take browserifys speed via watchify anyday

cphoover• 8 years ago

webpack is a monolithic build tool.

I prefer substack/browserify's unixy approach to software design.

Announcing TypeScript 3.0 RC

Related Stories