www.codinghillbilly.com   kyle.baley.org  Subscribe / Contact
 
 
 
 
LATEST POSTS
Sunday, September 02, 2007

I recently attended John Bristowe's presentation on Silverlight. He was great as always and gave a good overview of the technology but I left the room not being as excited about Silverlight as I was when I went in.

Which isn't to say I'm not stoked about it. I'm a big AJAX fan and the idea of doing some of the more complicated or labour-intensive stuff in managed code is appealing. But there has been a tremendous amount of buzz on Silverlight. I've been following Tim Heuer's recent adventures in it with a tinge of jealousy because I'm still not playing with it a lot. And when Ray Ozzie touts the next big thing, people listen.

I had done my own "hello world" app early on and was suitably impressed. In the intervening months, the buzz just kept growing and growing to the point where I went into the presentation trying to see what else there was to it. I knew it was being positioned as a Flash-killer (or at least that's what the buzz was) but I had to see what I had missed in my XAML.

Turns it out, not much. Yes, it's a Flash-killer (whether John wants to say the words or not) but as far as I can tell, that's it. At the end, I was scratching my head about why everyone was so worked up about it. You're still working with textboxes and input buttons and wiring up the events the same way you would in HTML and Javascript, albeit in a *much* easier way. And probably prettier too once the designers get hold of this. You still have the same security limitations of Javascript. In particular, you still can't call webservices outside your domain. (This was one of the problems I thought Silverlight may have solved. They're working on it but for the moment at least, you still need to call back to your own domain.)

The essence of my puzzlement is that I don't understand why so many people think this is going to revolutionize the web. I mean that as a genuine question, not a cynical dig. Is it because of the presentation-aspect? That Silverlight can make apps that much more appealing visually? If so, how is it different than Flash? To be sure, the airline demo *is* impressive (and I sincerely hope someone is making an effort to do a real-world version of it).

I dunno, maybe I am underestimating the popularity of Flash. It doesn't seem like a very threatening technology to kill off. I'm probably not recognizing the value of the media-centred features of Silverlight as well. This is probably the big selling point for the executives at Microsoft, especially in an era where YouTube can be sold for $1.65b.

More likely, I'm probably underestimating the pain new web developers are feeling trying to get Javascript to do things people have come to expect from their web apps. Early in the presentation, John asked, "Who *likes* working with HTML, CSS, and Javascript?" It was a loaded question and I didn't want to get him off-track early in the presentation but to be honest, I do. Not at the expense of "real" development but I actually don't mind diving into Fiddler with XMLHTTPRequest objects, spewing alerts all over the screen. Not all day, every day but I like mucking with the DOM in a crappy dynamic language once in a while. It's my version of slumming it.

Silverlight is still in the top three on my technology wish list. I can think of quite a few applications that could benefit from it, not the least of which is the near-defunct music player I work on in fits of ambition. So I'll fiddle around with it in the coming months because it fits with my sensibilities. And if I'm lucky, it'll be as popular as everyone says it will and I'll be able to keep the young'un fed for the next couple of years.

Kyle the Aligned

Sunday, September 02, 2007 1:21:11 PM (Eastern Standard Time, UTC-05:00)
This continual "who likes working with HTML, CSS, and Javascript" line is one I've heard before, and I have serious issues with it. I think if you are a web developer, you should actually have some sort of clue about the technologies you're working with; and with some knowledge it's certainly not that painful at *all*. I feel as if that really plays up the "let's dumb this stuff down" card quite a lot, myself.
Sunday, September 02, 2007 9:51:58 PM (Eastern Standard Time, UTC-05:00)
Well, to be fair, there's a fine line. After all, one could ask, "Who likes writing data access code?" or "Who likes rolling their own inversion of control container?" But I agree with you for the most part. People don't necessarily need to be proficient with XMLHTTPRequest objects to love ASP.NET AJAX but I think it helps to know exactly what it's abstracting.

As for Silverlight, there are clearly things that it will be able to do that I wouldn't even begin to attempt in HTML and Javascript. Nice, flashy (with a lowercase 'f') things. And it's nice that you can communicate back and forth 'twixt Silverlight and Javascript. Like any tool, it's best used for what it's good at and not because the alternative is "too hard".
The Coding Hillbilly
Tuesday, September 04, 2007 7:20:31 PM (Eastern Standard Time, UTC-05:00)
These are totally fair points. And I agree: It was a loaded question. My intention was to draw a comparison between developing in CSS/HTML/JavaScript versus .NET. I will admit that I'm jaded; I built Websites for years and absolutely hated the cross-browser/cross-platform issues I faced. Also, I always felt handcuffed by the sandbox I was provided. Often times, there were things I just couldn't do. At the end of the day, it's all about trade-offs. For example, you can't beat the Web deployment model. Period. And don't get me wrong; Silverlight isn't perfect... yet. ;-) As it stands right now, you still have to do a fair bit of heavy-lifting to get things done. This will improve, no doubt.

Thanks for your review. I'm sorry you felt a little less impressed about Silverlight. Perhaps you and I could have a chat about specifics. Hopefully, that might win you back. :-)
Tuesday, September 04, 2007 7:40:39 PM (Eastern Standard Time, UTC-05:00)
Well, I want to re-iterate that I'm still plenty excited about it. The same way I was when Atlas was announced. So winning me back will be pretty easy because I'm already won over. I'm just wondering why the likes of Ray Ozzie are touting this as a revolution while, for example, ASP.NET AJAX has to win its accolades on merit alone.

And again, I don't mean that to sound like Silverlight doesn't deserve its hype. More that I don't understand it. And Jayzus knows it wouldn't be the first time.
The Coding Hillbilly
Comments are closed.

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Copyright © 2010 Kyle Baley. All rights reserved.
 
CATEGORIES
.NET General (18) alt.net (4) altnetconf (9) ASP.NET AJAX (40) ASP.NET MVC (29) Bahamas (1) Bahanet (9) BDD (1) Brownfield (21) Career (10) Castle (1) Code coverage (1) Code review (2) Coding Style (6) Communication (1) Community (18) Conscientious Coding (35) Continuous Integration (11) dasBlog (12) Development (16) DevTeach (4) Domain (2) Environment (4) Estimating (1) Featured (14) Flamingo (10) Games (1) Google App Engine (3) GWT (9) Hardware (6) Java (2) Javascript (7) Linq (2) Livelink (6) Lucene.NET (2) MbUnit (1) Metrics (2) Miscellaneous (25) Mocking (4) NAnt (4) NHibernate (12) NInject (1) Office (3) Office Development (6) Open Rasta (1) Patterns (6) Presenting (14) Professional Development (15) Refactoring (10) ReSharper (11) REST (3) S#arp Architecture (5) Security (3) Software (11) Sundry (19) TDD (19) Tools (22) User Interface (6) Utilities (9) Visual Studio (8) VSTO (1) Web development (12) Windows (3) Working Remotely (17) Workplace (3) Writing (6)
 
LATEST POSTS
 
POPULAR POSTS
 
 
ARCHIVE