31–40 of 142 posts
Good riddance. And once again, all the companies that decided to rely on a proprietary, non standard technology are going to get bitten.
Plenty of companies out there are still using VB6. It's not like Microsoft is going to take away the download or something, they'll just stop developing it.
Also, why "good riddance"? Do you just hate everything Microsoft or did Silverlight really cause you any problems personally?
I "get" it when it comes to silverlight for public facing websites. Really. I do. The general populace doesn't want to have to install a plugin. But what about intranet apps? Silverlight is so incredibly easy to work with (compared to html/css/js) that there are lots of companies that have built intranet apps with it because they control the end point. I really hope this isn't true.
One really important reason is not to tie your intranet to the Silverlight/Flash/runtime N roadmap. Better to hook up to something that will run in browsers without painting yourself into yet another proprietary corner.
I "get" it when it comes to silverlight for public facing websites. Really. I do. The general populace doesn't want to have to install a plugin. But what about intranet apps? Silverlight is so incredibly easy to work with (compared to html/css/js) that there are lots of companies that have built intranet apps with it because they control the end point. I really hope this isn't true.
> But what about intranet apps? Remember when IE6 was so incredibly easy to work with? Remember how much effort has been dedicated to port those internal "web applications" that worked on one specific browser?
I "get" it when it comes to silverlight for public facing websites. Really. I do. The general populace doesn't want to have to install a plugin. But what about intranet apps? Silverlight is so incredibly easy to work with (compared to html/css/js) that there are lots of companies that have built intranet apps with it because they control the end point. I really hope this isn't true.
But why require your developers to learn another set of technologies? Much better IMHO to just have a good web development team who can make internal applications too.
Nobody should ever invent a competing technology because HTML is good enough for you? Is that it?
I look forward to our new HTML5 overlord.
Earlier quoted context omitted.
> But what about intranet apps? Remember when IE6 was so incredibly easy to work with? Remember how much effort has been dedicated to port those internal "web applications" that worked on one specific browser?
You're comparing apples to oranges. IE6 is a browser, Silverlight is a plug-in. Using Silverlight doesn't mean that you can't switch browsers.
"Any application that can be written in JavaScript, will eventually be written in JavaScript."
http://www.codinghorror.com/blog/2009/08/all-programming-is-...
Earlier quoted context omitted.
One really important reason is not to tie your intranet to the Silverlight/Flash/runtime N roadmap. Better to hook up to something that will run in browsers without painting yourself into yet another proprietary corner.
Yeah, let's have a richly, wonderful, HTML interface that still can't replicate desktop GUI productivity from the 90's...
People who only do web dev just don't know what quality is.
Earlier quoted context omitted.
One really important reason is not to tie your intranet to the Silverlight/Flash/runtime N roadmap. Better to hook up to something that will run in browsers without painting yourself into yet another proprietary corner.
Yeah, let's have a richly, wonderful, HTML interface that still can't replicate desktop GUI productivity from the 90's...
OTOH, you may be tied to IE6 and unable to see all this.