About/Contact

Steve Trefethen

Steve Trefethen is CTO at Wanderful Media.
Contact me

View my LinkedIn profile



Calendar

<<  June 2013  >>
MoTuWeThFrSaSu
272829303112
3456789
10111213141516
17181920212223
24252627282930
1234567

View posts in large calendar

Disclaimer

The posts on this weblog are provided AS IS with no warranties, and confer no rights. The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.



TypeScript what was the problem again?

October 02 2012 11:25PM

A friend pointed me to the release of TypeScript and the video where Anders Hejsberg provided an explanation and multiple examples of Microsoft’s latest efforts to improve JavaScript development. For me personally the video is a real throwback to the days attending team meetings at Borland where Anders would demo Delphi language features. In fact, there’s an interesting parallel between TypeScript and Delphi where both require proprietary interface files to call functions in external modules with the same issues of getting these files generated/updated.

I’ve been working in the OS world for the last few years now and I’m left scratching my head wondering where this effort is going? It places huge emphasis on Intellisense and error insight features yet ignores how one might approach actually debugging all this beautifully unfamiliar generated code. Throughout the video I kept asking “Why wouldn’t they simply offer their own Dart-like alternative?”

While it “feels” fun and has the ususal Anders demo props going for it seeing a compiler infer types simply isn’t as exciting as it was the first go-round and the lack of a debug session demo left me feeling rather hollow. Had MS released an updated IE natively supporting TypeScript… but no we’re not back in IE 3 days, that ship has sailed.

Perhaps it’s an Enterprise play to help those lowly Enterprise developers conquer JavaScript in a way that’s more palatable by management? Ah, I don’t think so as it’s all interestingly packed as Open Source.

Don’t get me wrong I appreciate type safety as much as the next compiler fan and in many ways I long for those good ol’ type safe days but I’m pretty skeptical that this is the right path forward.

FacebookDel.icio.usDigg It!

Comments (5) -

10/3/2012 6:00:50 AM #

Without making any comment on TypeScript, isn't debugging a solved problem with source maps?

http://www.youtube.com/watch?v=-xJl22Kvgjg

Craig Stuntz United States

10/4/2012 8:51:02 AM #

If the debugging problem had been solved I'd have expected that to have been covered in the Demo. Google certainly has put forth something but what's MS' story? GWT has been around a long time seemingly solving the development issues raised in the video hasn't it?

Steve United States

10/15/2012 5:27:46 PM #

Steve --

I believe that Javascript is the "new assembler".  That is, we'll write higher level language code and compile it down to Javascript which runs on the "new OS", i.e the browser.  

And so TypeScript is an attempt to create a language that is an order "higher" than Javascript.  

But that then raises the question -- why not just compile C# to Javascript?  

Nick

Nick Hodges United States

11/28/2012 10:45:38 PM #

Hey Nick!

> But that then raises the question -- why not just compile C# to JavaScript?

I think this hits right at the heart of the title I chose for this post.

Steve United States

11/28/2012 10:46:37 PM #

Btw, MS already compiles to JavaScript with Script# though they never seemed to want to throw their weight behind that effort.

Steve United States

Add comment




  Country flag
biuquote
  • Comment
  • Preview
Loading