Live data from Hacker News

Microsoft may halt development work on Silverlight plugin after next release

theverge.com

141–142 of 142 posts

Re: Microsoft may halt development work on Silverlight plugin after next release

#141

Earlier quoted context omitted.

So you don't use any proprietary technology then? What kind of car do you drive?

Of course I do. But I avoid it whenever it's possible and active advocate for non-proprietary alternatives.

That's cool with me. I choose technology on quality alone, with regards to my use cases. I certainly don't tell people that they shouldn't use what they're using, I just give my opinions. People such as yourself are often telling me I shouldn't do this or that. I don't mind it, because I enjoy talking about technology and sharing my point of view. Some people just don't see it though.

I think that I understand why someone would wish to exclude all proprietary technology. No advocacy is the best advocacy though. If the product is so great, it sells itself. It does. People use 'nix all the time for the things it's good at and then they go use other stuff too. Hostility towards that "other stuff" really works against the cause IMO. Why not spend the same time an energy to make the product better? Then people will just use it and nobody will have to argue about it.

Re: Microsoft may halt development work on Silverlight plugin after next release

#142
post #117

Earlier quoted context omitted.

If from a developer's viewpoint, XAML looks identical to Silverlight, and there are the same number of people working on XAML for the Windows team as there used to be working on Silverlight for DevDiv, does it matter? But I bet you're feeling betrayed. I understand. I felt a little betrayed a few frameworks ago. Post-betrayal, I stick to focusing on transferable skills and JIT learn the rest of .NET. I'm on a WPF pro…

I assumed that XAML was the silverlight team (why duplicate effort) and if silverligth is gone how much core knowledge stays in XAML? Personally I stuck to C++ and moved MFC->wx->Qt ! .Net is interesting for the way it allows things like Ironpython and F# in as first class languages and wpf is fun to play with, but if you can't write something like Office or photoshop in it then it's just a toy.

There you go, no problems then.
Post reply on HN