Lee Dale

6 days ago, BitCrazed wrote

Holy cow! I think something went wrong with the audio encoding on these videos - sound is totally overdriven.

Shame since this is a great session!

The sound is awful and makes the video a complete headache to listen to.

I think what alot of people complaining about are missing is the fact that most developers who are stuck within the Microsoft development stack and don't really look beyond it just open up Visual Studio and use whatever Microsoft puts in front of them.

I don't think this is created to fix or replace Javascript but to allow developers to work on Javascript code and be A) more productive and B) safer in the use of the language i.e. not getting themselves in trouble with dynamically typed languages.

We forget that there are many many developers out there that just want to build LOB applications the quickest and safest way possible.

I like the fact that it compiles down to standard Javascript and if developers adopt TypeScript then they are not stuck with alot of code that Microsoft might abandon several years down the line (*cough* Silverlight *cough*).

Anyway I think it looks cool to me, I personally prefer statically typed languages and adding type safety (at compiler level not runtime) makes me happier.  I work mainly with back end enterprise applications and I see alot of rubbish javascript, I'm not saying Typescript is the answer to this but it might help a little.

Anyway I don't think this is necessary a bad thing just another way of getting things done within the MS ecosystem.

...

irascian wrote:

Well that was embarrassing.

Just in case anyone's interested the Larkware site that Dave mentioned (which each day summarises interesting stuff found on the web for .NET developers) can be found here: http://www.larkware.com/ - definitely worth subscribing to their feed and checking the daily update if you're a .NET developer.