Architecturally how dead is Silverlight?
Earlier in the week I cancelled my order for Pro Silverlight 4 in C# and ordered Pro HTML5 Programming: Powerful APIs for Richer Internet Application Development. After spending a few hours with Pro HTML5 Programming: Powerful APIs for Richer Internet Application Development I reordered Pro Silverlight 4 in C# this morning.
I got to also spend a few hours with the PDF ebook version of Pro Silverlight 4 in C# yesterday that a friend bought. There are a few new chapters. One on File Access and one on Out-of-Browser Applications. I also read a new section on commands. The book looks great. Look for a review in a week or two.
I am currently lucky enough to be doing a Silverlight SharePoint web part project which is still a go. Anyone who has had to work with SharePoint web parts knows what a mess they can become. Silverlight allows for well architected and clean coded solutions. It also integrates very well with the SharePoint API.
As far as using Silverlight as a far reaching Internet application goes, it is off the table until I hear Microsoft recommit. I don't think they will. Reading all the posts from the Silverlight gurus out there reaffirmed that. So externally I will push for ASP.NET or MVC. As for internal Intranet applications go, I will still push for Silverlight. If they want it in ASP.NET, MVC, or HTML, they can go get a browser lover to do that. I know the browser was responsible for the success of the web, and it still is, but when you control the network and the boxes on it, going browser is just an anti-pattern and a poor architectural choice.
I am still baffled by PDC 2010. Personally I would fire (or move to another job) the people responsible for orchestrating it. I know Bob made an ID ten T error (ID10T), but the impact was so great because it was on the tail end of a horrible message sent from PDC.
So... Architecturally Silverlight is still alive and well. I can't speak for the money men and women though. Only time will tell how much damage was done to the image of Silverlight. So far in my camp it has been a 50/50 split. One project still a go, one cancelled.
I got to also spend a few hours with the PDF ebook version of Pro Silverlight 4 in C# yesterday that a friend bought. There are a few new chapters. One on File Access and one on Out-of-Browser Applications. I also read a new section on commands. The book looks great. Look for a review in a week or two.
I am currently lucky enough to be doing a Silverlight SharePoint web part project which is still a go. Anyone who has had to work with SharePoint web parts knows what a mess they can become. Silverlight allows for well architected and clean coded solutions. It also integrates very well with the SharePoint API.
As far as using Silverlight as a far reaching Internet application goes, it is off the table until I hear Microsoft recommit. I don't think they will. Reading all the posts from the Silverlight gurus out there reaffirmed that. So externally I will push for ASP.NET or MVC. As for internal Intranet applications go, I will still push for Silverlight. If they want it in ASP.NET, MVC, or HTML, they can go get a browser lover to do that. I know the browser was responsible for the success of the web, and it still is, but when you control the network and the boxes on it, going browser is just an anti-pattern and a poor architectural choice.
I am still baffled by PDC 2010. Personally I would fire (or move to another job) the people responsible for orchestrating it. I know Bob made an ID ten T error (ID10T), but the impact was so great because it was on the tail end of a horrible message sent from PDC.
So... Architecturally Silverlight is still alive and well. I can't speak for the money men and women though. Only time will tell how much damage was done to the image of Silverlight. So far in my camp it has been a 50/50 split. One project still a go, one cancelled.
0 Comments:
Post a Comment
<< Home