30 Jan 2013 12:03 PM #91
That said, compiler errors are only part of the benefit. The other huge area where this would help is around tooling/IDE support. Sencha's done some cool things with their Eclipse plugin, no doubt. But anyone who's worked with Java or Groovy using IDEA or Eclipse, or C# using Visual Studio, knows that Sencha's plugin is barely scratching the surface of what is possible. And all of that power is predicated upon some kind of type inference.
It also doesn't help that for reasons I'm still unable to fathom, Sencha is limiting the ability to buy their Eclipse plugin. But that's a completely different topic/rant.
30 Jan 2013 3:47 PM #92
30 Jan 2013 4:07 PM #93
30 Jan 2013 4:14 PM #94
- Join Date
- Mar 2007
- St. Louis, MO
- Vote Rating
Errors during "compilation" makes me think that you could do something with Sencha Cmd. You can add plugins to do JSLint/JSHint to get the bulk of it and maybe even do extra stuff.Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services email@example.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
30 Jan 2013 4:36 PM #95
A modern IDE also implements continuous background compilation in addition to a manual formal compile step. The moment I write a bad line of TypeScript the background compiler warns me with a red underline squiggle.
30 Jan 2013 5:46 PM #96
Beyond that, it seems like a TypeScript definition file is really, really low-hanging fruit. Creating one would be far easier than modifying Cmd. And with the definition file, you immediately open tons of capabilities in IDEs that support TypeScript (namely IDEA and Visual Studio). In other words, it would sure seem a lot simpler to take a few days and create a definition file, than take weeks or months to update Cmd.
30 Jan 2013 8:56 PM #97
Regardless, the fact of the matter is that any time spent compiling is time that is taken every time I want to make a change. Don't get me wrong. Compiling brings plenty of benefits. There are benefits to both systems. But for me, I know it would cost me more time compiling than finding the few extra little things jshint doesn't tell me. I spend very little time tracking those down.
30 Jan 2013 9:59 PM #98
31 Jan 2013 12:17 AM #99
31 Jan 2013 12:17 AM #100
You also get these free plugin features that just start with typescript support ...
Most VS users also buy the Resharper plugin that adds heaps more goodies ... and specifically some useful JS refactoring. The addition of typescript will inevitably grow this feature set much further as they leverage the type metadata.
So the point is ... that a large percentage of Sencha developers will not choose Eclipse and will inevitably be hanging out for Sencha supported typescript and may even consider other JS frameworks rather that abandon their favorite IDE.
I would also suggest that the Sencha team consider packaging their SDKs as a NuGet autoinstaller. Many .NET devs start exploring web tools by downloading these packages. Many more would discover Sencha if you shipped your GPL product in this format.