235 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Peter commented  ·  June 15, 2011 5:22 p.m.  ·  Delete

  It is highly disruptive of Microsoft to cause such confusion about their key development technologies. Especially since Silverlight / WPF and .NET in many ways define what is so advantageous about the Microsoft platform. And, as many others have said, have so much potential to win any multi-platform battle if Microsoft committed to it.

• Ryan commented  ·  June 15, 2011 4:38 p.m.  ·  Delete

  Please make Silverlight the primary development platform for the new Win8 application model. It deserves to be a first class citizen and shouldn't take a back seat to any other technology (Especially HTML/JS) as far as Windows app development is concerned.

• Alexandre commented  ·  June 15, 2011 11:49 a.m.  ·  Delete

  of course it would need to be multiplatform and in/out of browser and access to all .net features including I/O even on macOS and android...

  I can't believe you don't give millions to those dude who are working mono. Actually it might be too late now. again your too late..

• Alexandre commented  ·  June 15, 2011 11:43 a.m.  ·  Delete

  Merged ultra fast multiplatform (iOS, MacOs, Android, Windows) Silverlight/WPF stacks with C#5

  is it SO HARD TO DO??? Why can't you see that this is what you should concentrate on right now... At least for now the Multiplatform and afterwards you need to recreate the underlying stack but still use the sames interfaces...

  Of course, XAML, Silverlight/WPF can be ameliorated in terms of usability but for now it's more than enough... You should concentrate on giving what devellopers want... a stable multiplatform multi-touch Silverlight/.net stack

  Adobe Air did it so why can't you?

  Are you waiting for Scala to run on adobe air or that google push Scala with android?? The only reasons .net programmers stay is because of the powerful languages features/tools/API, once other create that + a better UI stack ish ... we the lost trust that we have currently with html5 i really wonder how much will stay "loyal" to microsoft

• borisper1 commented  ·  June 15, 2011 4:37 a.m.  ·  Delete

  .net is more powerful than HTML5 and JavaScript

• Anonymous commented  ·  June 15, 2011 1:46 a.m.  ·  Delete

  Silverlight

• Ayo commented  ·  June 14, 2011 2:57 p.m.  ·  Delete

  Silverlight, WPF, .NET...all the WAY!!!!

• Tom commented  ·  June 14, 2011 12:16 p.m.  ·  Delete

  Microsoft rarely innovates. Silverlight is an exception, a brilliant technology that, if properly leveraged, will allow Ms to compete against the fairly abysmal tools offered for iOS and Android development. Don't give up, Ms, dig in!

• star commented  ·  June 14, 2011 9:02 a.m.  ·  Delete

  Silverlight, WPF

• 林昌鑫 commented  ·  June 14, 2011 2:36 a.m.  ·  Delete

  Silverlight, WPF

• wangzhen commented  ·  June 13, 2011 6:15 p.m.  ·  Delete

  My English is very poor,so I copied to show my idea.
  I like open standards, but they evolve very slowly. That's why we always need Silverlight as .NET developers. We don't want to go back to the dark ages of programming in HTML, JavaScript, CSS, etc. Any idiot at MS who doesn't realize the elegant nature of Silverlight (both XAML and C#) must be fired!!

• Anonymous commented  ·  June 13, 2011 5:21 p.m.  ·  Delete

  i live silverlight !3Q

• John commented  ·  June 13, 2011 9:47 a.m.  ·  Delete

  As far as Silverlight relates to web development, I feel it is couterproductive to open standards for MS to pursue this.

• Mark Jones commented  ·  June 13, 2011 7:12 a.m.  ·  Delete

  Some points I've previously mentioned are resurfacing, which is great, so I'd like to briefly chime in here in response to some specific recent comments.

  The differences between HTML5 and Silverlight which are of primary importance are the most conspicuous apples and oranges we're trying to compare here. So to take a short crack at explaining those differences ...

  First, in all this discussion I think it's very important to recognize the real distinctions both in SCOPE and PURPOSE between HTML5 and Silverlight. In a nutshell, HTML5 is an emerging, new presentation platform that has in recent history been designed as a much richer, more powerful platform for WEB applications, primarily relying on and living within a very thin, isolated user-experience layer. By contrast, Silverlight has always been presented as an added-value, great-equalizer UX platform for GENERAL applications, whether or not they are hosted in a browser or whether they are running within a particular OS. HTML5 was certainly never be intended as a GENERALIZED application UX platform (although many individuals will try to shoe-horn it into that role). This more generalized UX role is where Silverlight really shines, and is clearly superior to HTML5.

  Secondly, many of you have also pointed out the other huge differences between SL and HTML5 -- power and ease of use. It's laughable in either of these all-important realms of power-vs-simplicity to try to compare HTML5 to Silverlight. Those who do not see the "it's-so-stupid-it's-funny" humor in that just need to gain some real, demanding application development experience with both platforms.

  The impacts of these differences on the software architect and developer are related to design complexity, coding effort, underlying, out-of-the-box capabilities, developer productivity, and system stability. The impacts on the users are feature set, ease of use, time to market, support cycles, deployment cost, and of course how-blasted-long it takes to get a usable product in your hands.

  But here's the rub: MSFT is now apparently positioning HTML5 as the end-all panacea of application user experience, even outside any web scope. In so doing, I believe they are exceeding the HTML5 design mandate and trying to get the presentation and input services of HTML5 to be the general UX platform for ALL sorts of applications, Web-apps, or otherwise. I think this is clearly a mistake.

  Further elaboration on the finer and practical points surrounding the differences between HTML5 and Silverlight do not belong in this thread, but I would just summarize it the following way: If Microsoft wants an application-UX platform that is well suited to generalized apps and is ideally suited for cross-platform compatibility, it should prefer Silverlight over HTML5, for the reasons I've stated here. I think Microsoft's current position which presents HTML5 as the UX platform of choice is a massive shoe-horning of web-application technology into the general user-application model. I can see an individual making this mistake, but Microsoft?

  Silverlight all the way

• Guille commented  ·  June 13, 2011 5:54 a.m.  ·  Delete

  kzu, it's very obvious that I'm not talking about ECMA C# when referring to the MS history apart from the standards.
  I think that all the discussion ends up (as almost always) in a trade-off between the different options (i.e. HTML5 is supported by W3C, SL evolves faster, etc.), and the final decision will depend on the criteria and context that the guys from MS are handling. I mean, both options have pro and cons, it's a matter to see how each is weighted by MS.

• Xshi king commented  ·  June 13, 2011 5:03 a.m.  ·  Delete

  Silverlight

• JohnConnor commented  ·  June 13, 2011 2:08 a.m.  ·  Delete

  我支持将Windows8支持Silverlight

• michaltina commented  ·  June 13, 2011 1:01 a.m.  ·  Delete

  My English is very poor,so I copied to show my idea.
  I like open standards, but they evolve very slowly. That's why we always need Silverlight as .NET developers. We don't want to go back to the dark ages of programming in HTML, JavaScript, CSS, etc. Any idiot at MS who doesn't realize the elegant nature of Silverlight (both XAML and C#) must be fired!!
  放弃.net,放弃silverlight将使微软走向灭亡.

• Anonymous commented  ·  June 13, 2011 12:47 a.m.  ·  Delete

  My English is very poor,so I copied to show my idea.
  I like open standards, but they evolve very slowly. That's why we always need Silverlight as .NET developers. We don't want to go back to the dark ages of programming in HTML, JavaScript, CSS, etc. Any idiot at MS who doesn't realize the elegant nature of Silverlight (both XAML and C#) must be fired!!

• 程凡 commented  ·  June 12, 2011 10:50 p.m.  ·  Delete

  是时候抛弃M$了,他不支持你,何必守着这棵枯树不放.