News for hackers. Stuff that matters.
Re:Microsoft has Abandoned Silverlight and All Other Plugins by rbanffy on Thursday September 15, 2011 @07:27AM (#2999782)
> The Open Source community has never abandoned any technology?

It's an apples to oranges comparison. It doesn't matter if Silverlight is popular (it's not). Microsoft decided it would not continue developing and that's it.

OTOH, Oracle may try as hard as they want to terminate MySQL. That won't work. We already have Maria and Drizzle to take its place.

Second example: Zope v2. When Zope Corp decided to invest their resources on Zope v3, the community that relied on Zope v2 (people who maintain Plone, ERP5, Zenoss and others) continued to evolve Zope v2, sometimes backporting and bridging between it and Zope v3. Zope v2 is still alive and well and, IMHO, kicks ass.

The only way to kill an open-source project is not to use it. When nobody does, it's dead. And even then, with the source code available, it can be brought back to life as soon as someone wants it.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by CWuestefeld on Thursday September 15, 2011 @08:38AM (#3000012)
It's an apples to oranges comparison.

Right back at you.

On the one hand, you're saying that once MS stops actively developing a product, it's over. But on the other hand, you say that anybody can pick up any old open source software that they're interested in?

Why isn't the same logic true for the MS platform? I mean, my copy of the .Net4 installer is just fine. Even if MS decided that the .Net would no longer be developed, what's stopping me from using what's already out there?

Re:Microsoft has Abandoned Silverlight and All Other Plugins by rbanffy on Thursday September 15, 2011 @08:48AM (#3000060)
> Why isn't the same logic true for the MS platform?

Because they won't publish the source code of discontinued technologies so that others can continue their development.

> my copy of the .Net4 installer is just fine. Even if MS decided that the .Net would no longer be developed, what's stopping me from using what's already out there?

I see you confuse being available (as in "I kept a copy around") with being alive and actively developed. You can't continue to evolve Windows 95 by yourself. That's not true with each and every open-source product or project out there.

BTW, try running your .NET 1.0 installer on an ARM-based Windows 8 machine and tell me if it works.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by CWuestefeld on Thursday September 15, 2011 @09:12AM (#3000142)
You can't continue to evolve Windows 95 by yourself.

Nor can most organizations continue to evolve open source project X.

try running your .NET 1.0 installer on an ARM-based Windows 8 machine and tell me if it works.

Same is true for OpenOffice or whatever.

The fact is that the vast majority of uses are not capable of contributing to open source code, let alone a complete, regression-tested port to another platform. For practical purposes, there is precious little difference between FOSS and proprietary software for most users: either what is currently available works for them, or it doesn't.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by octopus on Thursday September 15, 2011 @09:34AM (#3000222)
The difference is that you personally can't recompile .NET 1.0 to run on a Windows based ARM (only Microsoft can do this if they decide it is in their best interest). On the other hand you can, if you want or need, recompile OpenOffice (or any open source project) on ARM - see for example how Ubuntu was ported to ARM!
Re:Microsoft has Abandoned Silverlight and All Other Plugins by rbanffy on Thursday September 15, 2011 @09:37AM (#3000243)
> Nor can most organizations continue to evolve open source project X.

Can you name any project X you feel fits your hypothesis?

> The fact is that the vast majority of uses are not capable of contributing to open source code

At least they can pay someone capable to do it. Can you find someone capable of evolving Windows 95? No, you can't. Source-code availability is critical for this.

If your company, for instance, depends on PHP3 (or Perl 3, or Python 1 or something similar) you'll find readily available talent that can either port your application to a modern version of whatever it needs, or add whatever functionality you require to the ancient product you depend on.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by CWuestefeld on Thursday September 15, 2011 @10:12PM (#3002905)
> > Nor can most organizations continue to evolve open source project X.

> Can you name any project X you feel fits your hypothesis?

That seems an odd question to me. Pick a random organization that is using some FOSS package. I bet you that this organization is not going to be prepared to evolve that system, either due to skills or to other resource issues.

How many companies out there are going to be able to port Python or LibreOffice or what-have-you to a new platform? Most don't have the skillset. But even if they did, they won't have the resources to keep the developer working on that rather than the internal projects. Sure, there are exceptions (and I'm glad there are), but those are just that: exceptions.

Even if the theoretical possibility is there, practical considerations don't allow it.

Most companies do not have the resources to contribute to FOSS, and even fewer companies actually do it.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by rbanffy on Friday September 16, 2011 @10:52PM (#3007086)
I find it extremely unlikely we would have to port something the size of LibreOffice or Python to a completely different platform. What we would probably be able to do would be to fix bugs that affect us, port it to newer releases of the dependencies it was originally designed for (or, if not possible, adopt the dependencies) and make small improvements if the need arises. What we could also do is to find other groups with similar needs and pool our resources. No closed-source system allows that.
Re:Microsoft has Abandoned Silverlight and All Other Plugins by crenshaw on Thursday September 15, 2011 @09:16AM (#3000160)
I see you confuse being available (as in "I kept a copy around") with being alive and actively developed.

I see you confuse source being available with being alive and actively developed. Sure, in theory, with source available its possible that someone pick it up and keep it alive. But often you either need a critical mass for that. MySQL may go on forever, but I can walk through the GitHub or SourceForge cemetery to find many dead bodies that will likely never be resurrected.

BTW, for many companies, you can often get the code in escrow. So if they discontinue or stop supporting the product, you get the source code.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by rbanffy on Thursday September 15, 2011 @09:46AM (#3000285)
> I can walk through the GitHub or SourceForge cemetery to find many dead bodies that will likely never be resurrected.

That's not the point - they won't be resurrected because nobody uses them anymore.

> BTW, for many companies, you can often get the code in escrow.

On one side you have a mechanism (open-source) that allows anyone interested to pool resources to maintain software after its previous maintainers abandon it. On the other, you see a mechanism under which you can, sometimes, get code that may or may not have been carefully maintained and may or may not have horrendous bugs you'll only become aware when you actually execute the contractual clause that allows you to get the source.

So, can we get the source for Windows 95? It's discontinued, right?

Re:Microsoft has Abandoned Silverlight and All Other Plugins by georgemcbay on Thursday September 15, 2011 @01:35PM (#3001235)
"You can't continue to evolve Windows 95 by yourself. That's not true with each and every open-source product or project out there."

This benefit is a lot more hypothetical than real. Practically speaking you can't continue to evolve Linux 1.2.0 (the version in the Win95 timeframe) yourself either. That's the fulltime job of hundreds of people. In both situations you're relying on those behind the project to evolve them if you want to use them as a foundation of other software.

And as the parent poster mentioned, in the real world you're far less likely to have had to evolve your own software to deal with changes in the underlying OS if you developed for Windows. Win32 apps that use the APIs correctly still work 16 years later. Good luck getting your coff/old-glibc/old-UI-lib Linux app from '95 running on modern Linux...

Re:Microsoft has Abandoned Silverlight and All Other Plugins by rbanffy on Thursday September 15, 2011 @04:21PM (#3001959)
In the real world, you are far less likely to have to evolve something the size of the Linux kernel (1.2 was, IIRC, orders of magnitude smaller than Win95), but it's really easy to continue maintaining smaller codebases (I pointed out Zope version 2 as an example of software that was obsoleted by their original authors but that has been evolving in the hands of a community that felt it would be too much work to port their software to Zope v3).

It also helps that so much of the mission-critical software you run on Linux is also open-source and can be easily recompiled. And you only need to recompile when the software can't run directly: I have Python code running in production that was written originally for Python 1.5.2. Oddly enough, lots of mission-critical applications are written in Python, Perl, PHP and various flavors of shell that run directly on more or less any *nix machine.

The fact is that dead ends in free software are so rare and so easy to get out of, this situation only rarely arises.

When it does, you can always weight your options and, sometimes, opt to go with a fork. Like I said, it has happened in the past.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by CWuestefeld on Thursday September 15, 2011 @05:05PM (#3002137)
And you only need to recompile when the software can't run directly

You've come around to actually making my argument! :)

As I said, as long as I have my installer for .Net, the software I write for that platform will still work.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by rbanffy on Thursday September 15, 2011 @05:45PM (#3002249)
> You've come around to actually making my argument! :)

Not even close. Unless you can recompile your .NET installer for a new computer architecture. If you can't, it's as dead as my Apple II word processor.

I can run that Python code on SPARC box I have. Can you do the same with your .net installer?

Again, since you seem not to understand, there is a difference between being able to install your jurassic .net framework on a current version of Windows and having its source code, something that would allow you not only to run it on current computers but also on almost any future computer that may possibly exist. Forever.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by CWuestefeld on Thursday September 15, 2011 @10:05PM (#3002890)
there is a difference between being able to install your jurassic .net framework on a current version of Windows and having its source code, something that would allow you not only to run it on current computers but also on almost any future computer that may possibly exist. Forever.

You're simply assuming that someone will continue to port Python 2 ad infinitum. Granted there's no reason to suspect that they will not (Except that at some point, Python 3 really catches on, and decades down the road people stop caring about 2. At that point you could port an interpreter -- but you won't, which is my point).

But there's also no reason to expect that I'll be unable to run my MS-based code. I mean, MS has ensured compatibility for, say, ancient Visual Basic code for forever. Real world experience shows us that there's no reason to be concerned about future compatibility. You're right that in principle it might be left behind, but experience shows us that this doesn't happen. The code I wrote 16 years ago for Win95 (and much earlier, for that matter) still runs.

That's the philosophical argument. The practical argument is Mono. It's open source, so anything good you can say about FOSS applies equally to .Net. It has the backing of both open source and corporate muscle. (although I have to grant that Mono doesn't cover 100% of the platform, I can plan my system to stay within those bounds)

Why is it that you assume that MS will dump backwards compatibility, but you're also willing to assume that someone will be interested in keeping and old FOSS platform alive (and that the tools to do so will still be functional)? It seems that in this argument, you want to have your cake and eat it, too.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by rbanffy on Friday September 16, 2011 @04:53AM (#3003695)
In the specific case of Mono, you are right and I would advise you to always plan to stay within its limits to ensure you have a runtime that you can maintain yourself if you really need to. As for future compatibility, remember, companies come and go and Microsoft won't be around forever. What did you do with your dBase II code and your Lotus 123 spreadsheets? In 100 years, Mono may be all that's left from Microsoft.

OTOH, I still find Mono a bit risky: I think Microsoft is capable of finding a way to kill it if it becomes too popular. They can't avoid it. It's their competitive nature.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by Pewpewarrows on Thursday September 15, 2011 @09:10AM (#3000136)
And what happens when .Net4 needs changes in order to evolve with the current ecosystem of products and platforms? Or just to run at all? That's right, you're shit out of luck. You go and learn a new tool and hope it doesn't happen again.

With Open Source you can always modify it to fit your needs, long after the original creators stop maintaining it.

I suggest you actually learn the difference between proprietary and open source projects before attempting to continue in this discussion.

Re:Microsoft has Abandoned Silverlight and All Other Plugins by rjbond3rd on Thursday September 15, 2011 @09:00AM (#3000104)
You can use it for a while, maybe a long while, without the source code.

But if you have the source, you can keep it going forever, rebuild a community of committers, add bug fixes, security fixes, new features.

Move to new architectures, add new abstractions, build your business on it without worrying that someone will arbitrarily try to kill it off...