Script# Vs. Google GWT: May the Best Ajax Tool Win (
Page 1 of 2 )
It's not clear whether Microsoft Web architect Nikhil Kothari's pet scripting project will become part of Microsoft's growing family of 'Sharp' languages. But his first Script# prototype is gaining traction.On the heels of Google's announcement of a Java-based development framework for Ajax, a Microsoft Web architect has unveiled a tool designed to provide C# developers with similar Ajax programming capabilities.
"Yep, I am finally publicly sharing a spare time project I've been working on the side in an off and on manner for some time now," blogged Kothari.
ADVERTISEMENT
Ajax is the name of a Web programming model, which translates roughly to "asynchronous JavaScript and XML." Adaptive Path, a Web design consultancy, coined the Ajax moniker. C# is Microsoft's object-oriented .Net programming language that many consider a head-to-head competitor with Sun Microsystems' Java.
Google, for its part, unveiled a rival Java development framework and tool, known as the Google Web Toolkit (GWT) at the JavaOne conference in mid-May.
Dion Almaer, an Ajax expert and co-founder of Ajaxian.com, said he believes Script# will go head-to-head against Google's GWT for developer mindshare.
"I think that Script# is combating the same need: Developers on platform X want to stay using the language/tools that they like," Almaer said. "If X equals Java they will use GWT; if X equals C# they will use Script#"
Microsoft's Kothari did not respond to a request by the time this article was published for additional information on how, when and whether Microsoft is interested in commercializing Script#. But Kothari did blog some details on his plans for his pet project.
"Essentially the Script# compiler is a C# compiler that generates Javascript instead of IL (Intermediate Language). A key driving goal of the design is to produce readable Javascript that you may have authored yourself, and would be ok deploying into real apps," explained Kothari.
Currently, Script# is not integrated with Atlas, Microsoft's Web client programming framework for Ajax, which is currently in beta test.
Kothari told one poster that he "still need(s) to figure out the exact Atlas story and how these two (Atlas and Script#) unify over time. As and when that happens, I am sure I'll blog about it…. currently these two aren't integrated as you note. There is a fair amount of work to be done before I can really get to things like LINQ (Microsoft's Language Integrated Query Project), and some of the other things you mention. Other projects: time will tell."
"Like Atlas, the idea behind Script# is oriented at providing an engineering approach and superior environment to developing applications using HTML/CSS and Javascript in a more productive, scalable and maintainable manner," Kothari blogged.
Some posters asked Kothari whether he planned to make Script# available on Microsoft's recently unveiled CodePlex code-repository site and/or release the code under a Shared Source or open-source license. He did not provide a definitive answer.
If Microsoft ends up bringing Script# in-house, it might opt to it as a Microsoft product – the way the company is planning to do with the IronPython programming language developed by Jim Hugunin. In 2004, Hugunin joined the Microsoft Common Language Runtime team, but he has continued to work on evolving the IronPython language from inside the Redmond software giant. The various IronPython beta builds are available under the Microsoft Shared Source license, and soon will be hosted on CodePlex.
Script# is another in the growing family of C# spinoffs under development by Microsoft and third-party entities. Microsoft Research is working on several such variants, including F#,Spec# and Sing#.
While many developers said they welcome tools like Script# and GWT with open arms, other programmers say they aren't so sure they will be the Ajax-development panaceas they are cracked up to be.
Ajaxian's Almaer said tools such as GWT and Script# are sometimes just too good to be true.
"I am not sure about the entire approach (Script#, GWT) and said so on," Almaer said. "I think that for a certain type of developer this approach can make sense, but it also scares me. It sounds great. Write code in C#, or Java, or ... and it all just works, right? We all know that isn't the case. A developer will try something and get: JavaScript error: line 2304. (However,) the developer isn't meant to know about the JS [JavaScript] piece. He can't debug it well as even if he goes to line 2304 it is gobbledygook that the framework spit out," Almaer said.
Moreover, "You also feel like since you are in Java you can use any Java class right?" he said, "No. You are really on the web so you only have access to a subset of libraries."
Dimitri Glazkov, in a comment posted on Kothari's Web site, agreed: "I gave it some more thought and I think the idea of Script# and GWT is abominable. It creates an abstraction layer where the developer doesn't need it. All this will do is create an opportunity for abuse. If you shield the developer from learning JS and knowing how it works, you will only get loads of insanely crappy code in return. It will work (some|most of the time), but it will cause countless hours, headache and induced hatred of technology of those who come behind."
Next Page: Script# Vs. Google's GWT: May the Best Ajax Tool Win
