We have worked out the schedule for opensource .NET talks at Skills Matter in London for the next few months. Here are the dates to note in your calendar – more detail on sessions will follow:
- 25th September: Script #, .NET response to Google Web Toolkit.
Registration is now open - 23rd October: Dependency injection with Castle Windsor
- 27th November: Asynchronous enterprise .NET applications with NServiceBus
- 17th December: Test driven development in .NET
We will probably do another Alt.NET evening in January like the one this July. This time we’ll have more time and hopefully a bigger venue. At the moment, we have a slot on 13th Jan available for this. If you attended the July talks, please let me know what you thought of the way that we organised it, what you liked, what you disliked, and what we could do to make it better next time.
|
|
Is Script# really comparable to GWT?
In terms of generating JS code from something that can be unit tested and debugged in a real IDE, yes. In terms of widgets and things like that, probably not. But I mostly used it to develop ajax sites in c# and generate JS from that.
Isn’t it a extremely leaky abstraction? I mean, don’t you have to fallback to the generated script to see what goes on?
Not sure where you got that impression. I used script# intensively at the place where I worked most of the last year, and the result did have some leaks but they were mostly due to the way we were mixing DOM objects and dynamic scripts, not specifically related to script# (anyway, I consider those bugs in browsers, not in script#). I certainly would not call it extremely leaky.