Why is everyone so surprised that Microsoft bundled a language that Microsoft built into a piece of software that Microsoft built? This says nothing about TypeScript's future among non-.NET developers.
TypeScript included with Visual Studio 2013 Update 2
41–50 of 111 posts
Re: TypeScript included with Visual Studio 2013 Update 2
#42Earlier quoted context omitted.
I think this is more directed at C# users. The focus of TS is to let tooling (specifically Visual Studio) do the same stuff it does in C#. They tried and failed to make VS good for JS.
I love VS for javascript. With ReSharper installed it is great. I guess maybe I answered my own question by admitting I need a JetBrains tool in there but: What tool is so great for Javascript? I use Sublime a lot as well on my Mac, and I don't like it as well.
Webstorm is pretty awesome for Javascript, but then again what else can you expect from JetBrains?
Re: TypeScript included with Visual Studio 2013 Update 2
#43Earlier quoted context omitted.
I like the ideas of Dart much more, but the JavaScript-interop is rather bad in Dart, because of the DartVM focus. TypeScript seems C# flange-mounted on top of JavaScript, but it's probaby the only viable alternative with good js-interop...
That's probably because TypeScript has more in common with CoffeeScript than Dart as a language. Dart is a full featured language that can stand on it's own and has it's own runtime. TypeScript is a superscript of javascript. It doesn't have a runtime - it gets transcompiled into javascript. If coffeescript is for writing javascript like you would write python or ruby, then typescript is for writing javascript like y…
> or maybe limited my use of TypeScript to just type annotations.
I was under the impression that was most if not all of typescript. What else remains? Classes?`
Re: TypeScript included with Visual Studio 2013 Update 2
#44While baking TypeScript into Visual Studio isn't a certainty of its future success (e.g. Silverlight), it is a good indicator of Microsoft's commitment to the language. As a former CoffeeScript user, I love TypeScript: it's a more consistent language driven by a real language designer, Anders Heijlsberg, author of Turbo Pascal, Delphi, C#, and now TypeScript. I am building 2 major projects using it: - RavenDB Managem…
The only thing needed now is a higher-level version of HTML... Something like XAML for instance.
Like HAML or Jade?
Re: TypeScript included with Visual Studio 2013 Update 2
#45I still don't quite understand why anyone would use TS... especially without an IDE.
Tooling is a big boon with TypeScript: Go to Definition, Find All References, Refactor->Rename, debug your TypeScript in Visual Studio. You're right that if you don't use the tooling, TypeScript is of lesser value. Using things like classes, lambdas, modules syntax is still there, of course, and is quite a bit nicer than JS equivalents.
Be careful with that if you use data-binding in your templates, such as Knockout.js . Visual Studio doesn't know the types of your viewmodels, so those templates are not indexed and not subject to refactoring.
Re: TypeScript included with Visual Studio 2013 Update 2
#46Earlier quoted context omitted.
That's probably because TypeScript has more in common with CoffeeScript than Dart as a language. Dart is a full featured language that can stand on it's own and has it's own runtime. TypeScript is a superscript of javascript. It doesn't have a runtime - it gets transcompiled into javascript. If coffeescript is for writing javascript like you would write python or ruby, then typescript is for writing javascript like y…
I haven't found any disadvantage to TypeScript over JavaScript. It's also trivial to switch, since compilation mostly just removes type annotations. I have however been annoyed at not being able to use sweet.js macros.
I'm still on an earlier version of TypeScript, so I don't know if later versions have fixed this. We ran into trouble when creating knockout view models in type script. Basically, TypeScript was losing track of 'this', and the trick of using var self=this in the the "constructor" wasn't valid. We made it work, but it wasn't pretty and it certainly wasn't idiomatic typescript.
Basically the problem was that we were trying to write TypeScript like we were writing C#, instead of treating typescript like a layer on top of JavaScript.
Re: TypeScript included with Visual Studio 2013 Update 2
#47Earlier quoted context omitted.
You don't need VS for TS. Eclipse and WebStorm support it pretty well. I've evaluated Visual Studio, Eclipse and WebStorm, and Eclipse and WebStorm are better for TypeScript development, at least if you're using Node.js.
I tried WebStorm and found their support for TS severly lacking, IIRC it was limited to automatic compilation and basic syntax detecting. Code understanding/static type analysis was basically non-existent, e.g. it wasn't checking if argument conforms the interface described in the method's definition - you had to compile the script to find that out.
It does check if the arguments are correct these days.
Re: TypeScript included with Visual Studio 2013 Update 2
#48Anyone using the Eclipse plugin? https://github.com/palantir/eclipse-typescript
Re: TypeScript included with Visual Studio 2013 Update 2
#49Re: TypeScript included with Visual Studio 2013 Update 2
#50Earlier quoted context omitted.
I think this is more directed at C# users. The focus of TS is to let tooling (specifically Visual Studio) do the same stuff it does in C#. They tried and failed to make VS good for JS.
I love VS for javascript. With ReSharper installed it is great. I guess maybe I answered my own question by admitting I need a JetBrains tool in there but: What tool is so great for Javascript? I use Sublime a lot as well on my Mac, and I don't like it as well.
Sublime + SublimeLinter-JSHint + Chrome DevTools