Mono Abandons Open Source Silverlight
mikejuk writes "The Mono project is about the only group of people actively talking up .NET and developing it, but in an interview Miguel de Icaza has admitted that Moonlight, the Mono version of Silverlight, isn't worth the effort any more. He said, 'Silverlight has not gained much adoption on the web, so it did not become the must-have technology that I thought [it] would have to become. And Microsoft added artificial restrictions to Silverlight that made it useless for desktop programming. These days we no longer believe that Silverlight is a suitable platform for write-once-run-anywhere technology, there are just too many limitations for it to be useful.'"
Now, if only Netflix would abandon it so that I don't have to boot into windows to watch movies...if it can be done for android, why not PC?
Bits of code, random ramblings: jakimfett.com
It just took a LOT of wasted time for him to believe it.
1) Create new technology
2) Market the hell out of it
3) Everyone gets hyped up, next big thing etc
4) Microsoft drops technology
5) repeat step 1
This has been their standard order of business for decades. Watch for the same thing to happen to "Metro" Microsoft's latest big thing..
Silverlight really is a well thought out technology. It does a great job of abstracting the presentation layer from the code, and is pleasant to program. The tools for developing in Silverlight are nice, too. Too bad that it is showing signs of fading away - I think it had a lot of potential.
My comments are my own, and do not represent the views of my employer, my spouse, my children, or my cats.
Am I a bad person to experience a Schadenfreude rush everytime Miguel, Facebook, Zynga or Groupon fails?
@de_machina
Hasn't silverlight been abandoned?
First release in '07 and according to the wikipedia article the staggering market penetration of 0.3% (thats zero point three, I didn't drop a leading 9 or something...)
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
I'm no fan of .NET, but I'm pretty sure the Mono developers aren't the only ones using it.
He is saying there is no future for Silverlight (the .NET based web plugin), not all of .NET. And that they won't put resouces into developing Moonlight (the open source version of Silverlight).
I know of two sites that use Silverlight, netflix and xfinity. They both use it just for the Microsoft DRM, afaik.
It isn't terribly surprising that Mono is abandoning Silverlight, since Microsoft seems to be doing much the same in favor of HTML 5.
The .NET Framework and tools in totality are a different story, though.
By the way, for those who haven't looked at it recently, MonoDevelop has come a -long- way. It's feature-comparable to Visual Studio, nowadays.
~ Whence do you come, slayer of men, or where are you going, conqueror of space?
This is just another sign of the industry converging to HTML5 as the primary display API. Flash is going away, now Silverlight is, too. Hopefully the companies will increase their efforts to allow users / developers to migrate existing applications to the new API.
If you want to watch many companies Ultra Violet distributors movies you're stuck with Silverlight, at the prompting of one I tried to get Moonlight going but there wasn't a 64 Bit version.
Of course Sony takes and overall screw Linux position even banning Linux browsers from logging into their website with cryptic error messages.
The preceding post was not a Slashvertisement.
Silverlight, and even Flash, are dying out.
Don't get me wrong - that is a good thing - but I want to be able to watch Netflix, Youtube Videos, etc. in my browser and that isn't going to happen unless there is some way for my browser to handle DRM'ed video streams.
So, either HTML5 needs to add support for DRM'ed video, or users will only be able to use these services via 'apps' and obscure platforms will be at a huge disadvantage (e.g. Netflix isn't writing an app for the Playbook because the platform isn't popular enough).
Personally, I think that the hate that is felt towards DRM should be redirected towards proprietary DRM so we can break down platform lock-in and give the obscure platforms a chance with the average consumer.
"we no longer believe that Silverlight is a suitable platform for write-once-run-anywhere technology, there are just too many limitations for it to be useful."
If only someone could have warned you, oh wait someone did, _everyone_ in the world who has paid any attention to Microsoft's behavior over the last 20 years.
Miguel has supported:
the Microsoft "partnership" with Novell (disaster for Novell in the community)
OOXML/docx (deliberately obfuscated format mess)
C# (has a constant vague patent cloud over it that he dismisses)
Moonlight/Silverlight (a patent-encumbered flash clone, in an era when flash is going away, now shown to be a bad idea)
I used to wonder if Miguel was a Microsoft plant, now I wonder if he just has a learning disability.
Silverlight just like Flash was only ever going to be temporary anyway. They were both technologies trying to do the same thing of abstracting the GUI to something that crosses OS versions, platforms, etc. Once Flash started giving way to HTML5, the writing was on the wall for Silverlight. Soon, I imagine, we will have native apps for things the need deeper/privileged access to the platform (phone, tablet, desktop, whatever) and web-style HTML rendering for everything else.
My lead developer wanted to adopt Silverlight a couple years back for a key application we were developing. I am sure he had strong technical reasons, but getting tied to a highly proprietary Microsoft technology just smelled bad. .NET is one thing, Silverlight scared the hell out of me. I pulled out one of my rarely used veto cards and I'm glad I did.
See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
"The Mono project is about the only group of people actively talking up .NET" -- You made this up, right? tiobe.com shows C++ at 9.8% and C# at 6.8%.
Silverlight (and XNA, and Windows Phone 7, etc) basically refer to overlapping collections of .NET libraries (often referred to as profiles) which different environments support. The set of libraries that Xamarin provides for Android development is a superset of the libraries available in Silverlight 4. However the intent isn't for you to write Silverlight applications that happen to run on Android. The idea is to write all your common code using the .NET Base Class Libraries (BCL; which are included in the ECMA standard), and then write your interface using (wrappers) around the native libraries for Android (or iOS or WP7 or Silverlight or WPF or ASP), for each platform you release on.
"Microsoft added artificial restrictions to Silverlight"
Uhm, what do we say now... let's try: We told you so!
How many endless debates in forums back in the day when Mono development started, all in vain.
I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
I get this funny little feeling that "Ultraviolet" will come to occupy the same in history footnote as as "DIVX"(the phone-home video player attempt by Circuit City, not the codec), "Flexplay", and "DVD-D"...
I can't think of any ways that the 'consortium' behind it could make it any more of a user nightmare; but they seem to be doing their best.
.NET never was that huge for desktop apps for most users, but it is HUGE in the enterprise world. HTML5 is the path for Metro tile apps, but Microsoft isn't abandoning all their enterprise customers with internal apps. .NET isn't going away. Mono in theory could allow these customers to shift to Linux, but I'm not sure anyone has really tried that.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
Do you say that about the StarOffice/OpenOffice/LibreOffice developers to make sure their products support Microsoft Office files.
How about those hard working people in the WINE project.
Heck those guys who make DOS BOX.
I for one would like much more positive community support from the Open Source community toward Mono. De-Windows .NET would open the door towards more cross platform applications.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
The funniest part about that Talk page is that "JimTheFrog" is, according to his user page:
So basically, that entire talk page is about the lead of that DRM-centric disaster defending what is fundamentally a customer-hostile technology. I'd call him a shill but he's probably tasked with "maintaining the message" on places like Wikipedia to make UltraViolet seem less fundamentally shitty than it is. And his dickish attitude towards Linux seems unsurprising, given that he
That's why the Nook Tablet came with a locked bootloader, whereas the original Nook Color spawned a large ROM'mer community. Netflix required it in order to let them use their app. I think I'd rather deal with DRM for paid downloads than have my whole device locked down.
Posted from my Android phone. Oh, I can change this? There, that's better...
LibreOffice is just file formats.
screw WINE and DOS BOX, virtual machines run windows for those who want it, with a far superior compatibiliity.
IT already has. Most people that buy a BLuRay disc that try to use the "UltraViolet Digital Copy" get pissed as it's already expired most of the time.
I get questions a LOT about it, I point the people at Handbrake and AnyDVDHD so they can make their own that will work on all devices and never expire.
Do not look at laser with remaining good eye.
And it's HUGE on patch Tuesday, especially if it breaks the update completely and is retried repeatedly until MS fixes it.
thegodmovie.com - watch it
Microsoft isn't deprecating .NET in favor of Tablet form factor Metro apps because that wouldn't make any sense whatsoever. .NET is usually used as a back-end technology, huge amounts of the web are delivered using .NET applications. You wouldn't use Metro for what you normally use .NET for, and vice versa.
Yes, certain media outlets have hyped the fact Metro isn't .NET as some kind of evidence Microsoft doesn't like .NET or whatever. You can safely ignore any media outlet that does that. I'm not saying there's no desktop stuff in .NET, there's plenty around, but that's not where the focus is in .NET world, any more than it's the focus in Java world.
You are not alone. This is not normal. None of this is normal.
From Miguel: "These days we no longer believe that Silverlight is a suitable platform for write-once-run-anywhere technology, there are just too many limitations for it to be useful"
Who was he trying to kid (besides himself) ? .NET was never designed to be "write once, run anywhere" and never will be (since Mono will never implement all the libraries of the Microsoft implementation). If you want "write once, run anywhere" then just stick to Java, which is designed for this purpose - and yes, it means it can't use every feature of every platform, eg. Windows, but at least your software will run. everywhere (which gives you a better return-on-investment since you can sell to Windows *and* Linux *and* Mac, etc).
How many of the posters here have developed software solutions that actually sell, that help make money? Being for open standards is great but if you want to put food on the table and gas in the car then you need to get paid. In a business environment it makes sense to choose the dominant platform and the development tools that are optimized for it. These happen to be MS Windows and Visual Studio. For a rich GUI application you can choose WPF for desktops and Silverlight for mobile. There is still Adobe Flash out there but its size and the Apple effect on smartphones/tablets have all but made it irrelevant on mobile. De Icaza and the gang opened up the iOS and Android platforms to .NET devs, which decreased the MS dominance to some extent. If you are an exclusive Java/C/C++ fan then you can just ignore the 8% .NET developers but that number is not so far from the 9.8% C++ developers. And BTW, I have developed and published Web apps (HTML5/CSS/JavaScript) for mobile and then I decided to stop wasting my own time.
IIRC, The Netflix CEO is still on the board of Microsoft. Though I am surprised it works on Android - too big to ignore, perhaps? Or just until the Motorola patent attacks bore fruit...
I missed that so far - you deserve many informative mod-ups!
No wonder he compared Linux to Mozilla 1.0 (which I liked back in the day BTW)
The preceding post was not a Slashvertisement.
As a developer that started learning Silverlight and later abandoning it (mostly for technical reasons in that Silverlight forces you to use an ascyronous model leading to racing conditions and UI insanity).
In any case I got out early enough that I didn't get burned by MS Silverlight Gingerbread House. I do still feel a bit like Hansel and Gretel.
The worst part about the UltraViolet fiasco - it could actually work.
Finally a DRM technology that (is supposed to be) platform agnostic, works on (ahem -non-rooted) portables as easily as it does PC's (and theoretically digital renderers). It's convenient (as long as the instructions are clarified), can be downloaded (to arbitrarily few devices) or streamed.
Take out the stuff in parenthesis and it's a tech that could actually work for both the content providers and customers.
The preceding post was not a Slashvertisement.
And Microsoft added artificial restrictions to Silverlight that made it useless for desktop programming.
Everyone tried to tell you this, that Microsoft would stab you in the back, Miguel, but you wouldn't listen.
--
BMO
And if you don't want to pay Microsoft?
No it isn't. There is nothing to replace ASP.NET in the pipeline and Microsoft are hardly going to rewrite Visual Studio, Sharepoint and Dynamics CRM in Javascript/HTML5.
HTML5 is the path for Metro tile apps
HTML5/JS is a path for Metro apps. You can also write them in .NET and C++. In fact, writing them in C# is the easiest of three, because Metro APIs are heavily asynchronous (continuation-passing style), and C# 5 has convenient syntactic sugar for CPS; whereas in both C++ and JS you have to write out callbacks explicitly as lambdas.
You wouldn't use Metro for what you normally use .NET for, and vice versa.
That doesn't really make sense - not only Metro and .NET are orthogonal technologies, but writing Metro apps in .NET languages is a fully supported scenario.
Note the term "normally use" and the rest of my comment.
You don't "normally use" .NET for desktop applications. Some people do, but I said "normally", not "ever". You would use Metro for desktop apps, however.
You don't "normally use" (actually, I think "ever" would work in this context) Metro for back-end, Enterprise web app type stuff. Some people may for reasons that are related to dominatrices and whips, but few would. The most common use of .NET is for back-end, Enterprise web app, type stuff.
You are not alone. This is not normal. None of this is normal.
they already have abandoned .NET - the new APIs for Windows 8 is called WinRT and its the only API supported. Its a native API meaning performance we never quite got with .NET.
However, there are wrappers for C# apps to consume WinRT APIs, so you won't notice too much of a difference, but ou will have some porting to do as they're not 100% compatible with the old .NET assemblies.
Java is the new COBOL, and that means it will survive for a long time. C# is the new Java, as MS seems keen on native stuff this decade. We'll have to give it a couple of years for industry to catch up to where MS is going, but catch up they will, so while there are a lot of C# jobs out there today, they will start to diminish and C# apps will become legacy desktop apps as the cool new stuff goes HTML5 GUIs with C++ cloud backends.
Its website advertises support for C# 3.
Most mobile games you play are using mono http://www.unity3d.com/ .
.Net has plenty of potential to become a good cross-platform system. It's too bad Microsoft shows no interest in having it achieve that goal.
The difference with the other projects you mention is that they have already accepted that MS has no interest in them succeeding, and they have found ways to operate successfully under those conditions. I'm not sure that's possible with .Net. An ecosystem needs developers, and how many cross-platforn developers want to use a system controlled by a company that does not value cross-platform support. For the most part, developers targeting .Net won't bother making sure their code works on Mono, and developers wanting real cross-platform support will look elsewhere. This leaves Mono in a very tough position.
Note that none of this implies I agree with hduff. I'm ignoring his comment an carrying on a meaningful conversation instead.
Games can be written 99% in OpenGL ES, and just the user controls will vary from platform to platform.
The part that needs to be rewritten are GUI panels, widgets, layout, etc. Since all these platforms have significantly different interaction models (not just appearance) then any attempt to use the same interface will result in very poor user experience. Furthermore, if you really do have an application that is just GUI forms, then it must not be a very complex, and shouldn't take long to redo.
A few weeks ago I started to manage the new VOD platform. It's local, working only in my country, so its name is not relevant here. Project was started by a movie distribution company, seeking diversification and alternative to their DVD sales business, without the technical competence. They hired programming company, deeply Microsoft-related (partnership and so on). As you can expect, the platform was based on .NET/Windows Server, using IIS Smooth Streaming with PlayReady DRM, and Silverlight player. Then the problems with interoperability have started, as CEO quickly discovered, this solution has not worked on his iPad or iPhone, nor the Mac OS X playback was free from errors (most people in the company are appleheads, after all its movie business).
I come to the company as the manager with technological expertise (working a few years as the hosting guy/web developer, mostly in open source technologies), to oversee the work done by these external programmers. Our business strategy was to rely on presence on many different platforms, but now we're locked in. Luckily we were able to come on Samsung SmartTV platform, but only due to PlayReady implementation on these devices. We find a developers to prepare for us iOS app (Apple devices are PlayReady certified) and Sony PS3 app (also PlayReady certified). The advisors declared that there is no chance in moving our platform to Android and Linux, because THERE ARE NO DRM SYSTEMS AVAILABLE for these platforms.
The problem is that we have partners building their own settop boxes with Android on board, who want to use our VOD service as the source of premium video content for their users. The Android app would be great, but we cannot stream movies from our catalogue without DRM protection. I know that DRM sux, and is easy to circumvent, but you know, its a requirement put there by major movie producers - we cannot ignore that.
With these restrictions, we're looking for technological solution to bring our VOD content to the Android, and if it could be possible, to desktop Linux (at least Ubuntu). I've found Google DRM system: http://www.widevine.com/drm.html. Does anyone here has expertise in working with it? Can we use IIS to stream content encoded with this Widewine DRM? Please give your advice, maybe the Flash-based solution would be better, at least AdobeAIR still works on Android?
Correction: ".Net HAD plenty of potential to become a good cross-platform system." .Net has been around since 2000 and it's still nowhere near cross platform. Even within differing versions of Windows itself. The only good cross-platform solution is still Java.
> These days we no longer believe that Silverlight is a
.NET either.
> suitable platform for write-once-run-anywhere technology
It took you HOW long to figure this out? It wasn't extremely obvious to you, for example, when you saw the original Silverlight announcement from Microsoft?
Better late than never I guess. At this rate it'll be 2105 before they finally realize there's absolutely no point in emulating
Cut that out, or I will ship you to Norilsk in a box.
How do you intend to De-Windows .NET when it is owned and controlled by Microsoft who have every reason (and prior form of doing so) to stop at nothing to ensure that any other version will never be quite compatible.
Many of the failures of recent Microsoft technologies are because the truth does finally sink in eventually.
It seems it already works. https://chrome.google.com/webstore/detail/deceagebecbceejblnlcjooeohmmeldh/details
I would still disagree with that. .NET is not used on the desktop all that often in "consumer space" - i.e. your typical home desktop (though even there there have been a fair few .NET apps over the years). But in enterprise, .NET WinForms apps are a very common sight.