Move Over AJAX, Make Room for ARAX
sasserstyl writes "eWeek reports that Microsoft's Silverlight platform will support Ruby client-side scripting, enabling ARAX — or Asynchronous Ruby and XML. Would be cool to have the option to script client-side in something other than Javascript. 'In essence, using ARAX, Ruby developers would not have to go through the machinations of using something like the RJS (Ruby JavaScript) utility, where they write Ruby code and RJS generates JavaScript code to run on the client, Lam said. "Sure, you could do it that way, but then at some point you might have to add some JavaScript code that adds some custom functionality on the client yourself," he said. "So there's always that sense of, 'Now I'm in another world. And wouldn't it be nice if I have this utility class I wrote in Ruby...' Today if I want to use it in the browser I have to port it to JavaScript. Now I can just run it in the browser."'"
Does yours?
Not only that, but they're not adding a language that's significantly different. They're not adding Java (which Google might appreciate) or C/C++, they're adding Ruby, which is a language very similar to javascript (certainly more similar than JS or Ruby are to Java and their ilk). Port a language with better scalability and modularity, not more of the same.
Are you a troll (perhaps even a shill) or just a schmuck? There's nothing seriously wrong with Javascript as a language, only with specific implementations, some of which are actually quite good these days.
I'm guessing you are just a troll, but I don't want anyone to think you're right or anything and I have a little time on my hands :P
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Why?
Why is this good to run Silverlight?
Running silverlight on anything non-windows is like shoving legal issues up someone's ass and waiting for them to cough out the settlement.
Ruby on rails also seemed to work just fine without siverlight...and as comments show, more languages in the mix is not a good thing.
So yes, people are trashing MS because there is something wrong with this. If MS did anything right, we wouldnt' trash MS, we'd praise them. In this case, as usual, they haven't done anything right. I'd be glad to praise MS if they actually did something that wasn't underhanded, but when was the last time you can recall them doing that?
Probably shouldn't feed the troll, but ...
His argument was against your assertion that 'everybody thinks javascript just doesn't cut it for current web apps'.
This plainly isn't true as lots of people are actually very impressed by the javascript language, and just a bit frustrated that IE6 / IE7 / IE on Safari work so differently to everything else. For internal work I just ignore IE, and target Firefox only.
Even Joel has praise for javascript - take a look at his 'Can Your Programming Language Do This?' article at
http://www.joelonsoftware.com/items/2006/08/01.html
A better option than Javascript would be great, but Ruby hardly looks like the best option. A much better use of time for Microsoft would be making their Javscript engine for IE more standards compliant.
What's so insecure about the MSIL(by which I presume you mean .NET) compared to any other environment(Java, Rails, PHP, etc)? I am really curious to know. I know this is Slashdot but please try not to reply with 'Everyone knows it is'.
This space for rent.