I am however suspicious of this concept – time to put my Microsoft trouble maker tinfoil hat back on.
I have mentioned numerous times that there has been this divide or chasm between Windows + Internet Explorer and WPF/Silverlight – that is to say XAML/C# vs. HTML5/JS/C++. It is pretty well documented on this blog and in other parts of the web, and there is not much more to discuss on this suffice to say Typescript is yet another win for the HTML5 camp and loss for the XAML/C# camp.
This Is the part where a Microsoft evangelist or product manager for the team(s) feign innocence and give you the usual “it’s about choice” speech. True it will be about choice; I just cannot help to think that with all that investment and work gone into C#/XAML mix that taking a few steps backward to prop up HTML5/TypeScript seems an awful waste of time and energy to date.
There is no doubt that I would personally adopt TypeScript/HTML5 when the time comes to write a HTML based solution, as to me it fits nicely with my desired development pipeline. I still think however, the entire web based development pipeline is around 3-5 years behind where XAML/C# is today (I will even throw in Adobe ActionScript/MXML into that mix as well).
My thoughts are simple
- Internet Explorer is still being regarded inside Microsoft as a standalone ecosystem. I am still nervous and not excited about this thus suspicious of Typescripts charter (that fork in the road for IE vs. other browsers in the parity/ubiquity story is still coming up ahead).
- HTML5 vs. XAML/MXML. I still roll my eyes at HTML5 mainly as when you’ve used both MXML or XAML in your day to day development then look at HTML5 one can’t but help see the HTML5 has not only gone of charter – yet again. If we are going to go full, tilt XML UI declarative then let us fold Resource Dictionaries into place instead of CSS / style tags and be done with it.
- Typescript reminds me of the days when Adobe/Macromedia switched from ActionScript 1.o to 2.0/3.0. You felt it was a move forward and the idea isn’t new, at the same time it took a long while for existing developers to cross that chasm of adoption. Hopefully it ECMA6 wont fall into that same vortex of pain.
In Summary, Typescript will be a hit amongst the .NET kids out there, I don’t think it will go beyond that but that’s ok as that’s a few million developers out there that it will influence. I think this is still setting the ground work for future Internet Explorer development going forward and stay tuned for more of that discussion.
To quote a friend who recently gave his thoughts on HTML/JS development instead of WPF/SL/Flex development
It is like getting a hand job from a crack addict. You know it is wrong, you know it is a substitute for what you really want and lastly once it happens you can never look your friends in the eye the same way again. It however got the job done.
(That was the clean version of that believe it or not).