Script#, the C# --> AJAX Framework: let the debate begin
Posted by: Clarity Blogs: ASP.NET,
on 06 Jun 2006 |
View original | Bookmarked: 0 time(s)
Nikhil Kothari, an architect on the Web Platform and Tools team at Microsoft, has released a pet project of his, based on a prototype creating during experimentation with expanding the Atlas toolset. His release, Script#, allows developers the ability to write AJAX scripting from the comfort of a C#-based Visual Studio environment. The tool provides intellisense and type-checking of script code, since it is written in C#; the framework then generates a .js file that handles the javascript implementation of your code, providing .NET developers the means to create AJAX script from the comfortable environs of the VS IDE.
Nikhil's release opened up a killer debate on his site, and I was hoping to continue it here: basically the pros and cons being argued are this:
Pros:
- Writing scripting code in C# allows non-JS savvy developers a chance to quickly create much richer applications
- This is another tool to prevent developers from reinventing the wheel for each new project, meaning more on-time deliveries & less cost to clients
- Developers with little js background can get started on features without poring through DOM definitions online.
Cons
- Does compiling C# into a JS library simply add another layer of abstraction to code, causing migranes for developers that are unfortunate enough to come into this project later? (the generated script is by design minimized, but could make bug fixes a nightmare)
- Do tools like this reward weaker developers by allowing them to glide by, without learning what is occurring under the covers?
- Are we really trying to eliminate JS? A lot of devs are very productive in it, and don't feel limited...in fact, they feel C# is the limiting factor
I'm all for creative tools, and I'll experiment with this one...kudos to Nikhil for spending his personal time to go after such a lofty goal, and for providing it to the public. Devs should keep in mind, though, that tools are meant to be just that, tools...it is a slippery slope to try to force one dev technology to replace another.... feel free to post your opinions here