5 ms·
Why do you believe in any technology that MS gives you? The Open Source community has never abandoned any technology? Really? For most people, most of the time
by gaius 15y ago
Why do you believe in any technology that MS gives you?
The Open Source community has never abandoned any technology? Really? For most people, most of the time, "you have the source code, maintain it yourself" is no more feasible than "start a company and buy that product from MS".
Their technologies are invariably doomed to obsolesence within about 2-3 years of their introduction
That, quite simply, is FUD.
- rbanffy 15y ago> 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.
- CWuestefeld 15y agoIt'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?
- rbanffy 15y ago> 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.
- CWuestefeld 15y agoYou 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.
- octopus 15y agoThe 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!
- rbanffy 15y ago> 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.
- CWuestefeld 15y ago> > 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.
- rjbond3rd 15y agoYou 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...
- Pewpewarrows 15y agoAnd 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.
- Roboprog 15y ago>>>> obsolescence within ... 2-3 years ... >> FUD Is it FUD? More like a minor exaggeration, but true in spirit.
- hvs 15y agoHow is it "true in spirit"? Microsoft is practically the definition of backwards compatibility.
- neilk 15y agoI clarified what I meant a bit above. And who said anything about open source? I'm not sure I agree that things are as dire, but even if they were that wouldn't affect the argument about MS.
- TheCondor 15y agoThe biggest difference between OpenSource and what's going on with Silverlight is that there is a lot more, possibly even complete transparency with the OpensSource and you have options. I think if you do just a minimal amount of investigation you can get a good idea if a project is healthy or not. Likewise, you ultimately do have the source, you can look at it, understand it and decide if you can maintain it on your own or not. There isn't even a straight answer with Silverlight. With Silverlight, they're going to suffer the same fate IBM did with OS/2. First they don't know what they want to do, it was a "me to" product because they thought Adobe was getting too powerful or worried about DOA JavaFX, it might live, it might die, they don't know. Second, they don't know what to tell develoeprs that have invested in it, these people don't retarget to your other technologies, many of them leave after getting burned like that. Mixed messages come out, "they're completely committed" but their actions might not suggest that. The third step, they will retarget it and say something like 'Silverlight is really for x,y,z applications' maybe throw in a little 'we never really intended for it to replace the web or flash.' Ultimately, they pull the plug, any other company might attempt to sell the technology to a 3rd party to try and breath life into it or to make maintenance money from the few true believers that are left, I've not known MS to do that and even if they did, the damage is done once the uncertainty starts. Just that fact that people are asking if Silverlight is dead pretty much dooms it. MS has 2 options, let it die or show some kind of overwhelming support and double down. Anybody know how many companies have really bought in to it?