Open Community vs. Open Code 141
snydeq writes "Recent silence regarding the future of OpenSolaris under Oracle's hand has InfoWorld blogger Savio Rodrigues questioning the relative importance of open code. 'Source code availability is a central factor in establishing trust in the open source community, as knowledge that the source is available can often allay fears about the future of a particular open source project or product. And yet, this trust can often be overstated,' Rodrigues writes. Members of the OpenSolaris community have been agitating for Oracle to clarify its plans for OpenSolaris in the wake of its acquisition of Sun, with some suggesting a fork as a way of severing ties. But, as Rodrigues points out, 'The community around an open source project or product can certainly be vibrant without having the resources to support a fork. In fact, this is true for many open source communities, which count numerous members, very few of whom would be qualified to develop the open source project further should a fork occur. Worse, even fewer would be interested in doing so.'"
Hmmm (Score:5, Insightful)
So the short and neutral for of this article is:
A company opening the source to a given product at a given time may decide that - upon seeing not enough external developers jumping on - that it may be not worth continuing this effort. And the "community of administrators and users" complains they dont have enough programmers to fork it on their own.
How to say: Congratulations. But you know that *working* open source ecosystems also include programmers.
Re:Hmmm (Score:5, Insightful)
Why would a 'weekend hacker' work on OpenSolaris when they could work on Linux instead?
That's the fundamental problem: OpenSolaris has user features that Linux doesn't -- assuming Oracle continue to support it I'm probably going to set up an OpenSolaris server in the next year or so because ZFS is better than anything Linux currently has -- but it doesn't really offer anything to the average 'weekend hacker' that Linux doesn't.
Even if it was made available under the GPL, I suspect most of the best code would be copied into Linux and then it would die off.
Re: (Score:3, Insightful)
By the time you get around to setting up that Solaris server, Btrfs will have stabilized through 3-4 more mainline kernel releases.
Re: (Score:2)
By the time you get around to setting up that Solaris server, Btrfs will have stabilized through 3-4 more mainline kernel releases.
Which means that about five years later it will be ready for production use :).
I am thinking of switching one of my non-vital Linux systems to btrfs before long to try it out, but the whole point of setting up a ZFS server would be for proven reliable storage.
Re: (Score:3, Interesting)
Also, haven't Oracle been supporting btrfs development? That may not be doing that much longer if they now own ZFS.
Obviously development would continue without such support as it is GPL and is important for Linux in the future, but perhaps not at the same rate.
Re: (Score:3, Insightful)
My guess is that Linux is more important to Oracle than Solaris. They'll probably keep developing both.
Re: (Score:2)
Yeah - I'm kinda watching that BTRFS. I like the idea of hotplugging more hard drives into a RAID array. Yeah, I know, technically, that's not what I'm doing, but that's the end effect. RAID 99+ anyone?
Re: (Score:2, Insightful)
At which point Linux will dump it for the latest shiny. Just like hal. Just like pulse audio. For all its benefits, the Linux dev model is like a parasite that often forgets not to kill its host.
Re: (Score:2)
Yeah. Solaris. I've downloaded and installed it a few times now. Both on hardware and in VM's. I play around with it, then end up deleting it. I don't do serious server work, and everything I need to do can be done quickly and easily in Linux. I guess that Solaris/openSolaris is important to some people, but not to the average geek. Certainly not to the average person, LMAO
It would be something of a shame if Solaris dies off - but I won't miss it a great deal. Weekend hackers? I think most of them
Re: (Score:1)
Re: (Score:3, Insightful)
Solaris
Re: (Score:2)
Yes, ZFS is very simple (the code is very clean and only a few thousand lines - a lot of them comment) but it desperately needs to be ported to other platforms. OpenSolaris is nice but the only reason I use it is ZFS. Imitation ZFS (Btrfs) might eventually become good enough for me to use it but the current feature set of ZFS is very attractive for just about anyone who needs to host multi-GB's of data. Other nice features of OpenSolaris includes their COMSTAR stack (make cheap hardware appear as very expen
Re: (Score:2)
Well, you can work on both. Just port ZFS and other useful stuff to Linux, and then forget about it. (Or the other way around, depending on which architecture parts you deem better designed.)
Re: (Score:2)
its not about weekend hackers, but about companies developing new solutions based on the system.
Re: (Score:2)
If you ever tried to use java.net anytime in the last couple years to host an open-source project, you'd know how close to true that is.
Re: (Score:2, Funny)
Re: (Score:2)
Have you looked at ESR? I think he meant to champion the "bizarre model".
The great FOSS army is too busy playing Warcraft (Score:2, Funny)
Re: (Score:2)
Linux leveled up meanwhile. OpenSolaris is noob, it needs to grind with an established party to gain some experience.
Re:Hmmm (Score:5, Insightful)
Spare time? Most open source programmers get paid for their work, and quite well. Companies pay programmers to contribute to open-source enterprise-scale operating systems because they don't want to be dependent on the likes of Microsoft, Sun, or Oracle. And it works out economically because those companies have been overcharging tremendously.
Re: (Score:2)
Spare time? Most open source programmers get paid for their work, and quite well.
[citation needed]. I know it's true for the Linux kernel and probably some other server software, but there's huge amounts of open source that I would be very surprised if someone was getting paid for. Some of the things Sun has been funding has been things where I'm not sure anyone would pick up on, at least not as a whole product. Sure, there might be the odd company that wants a little feature in OpenOffice here and an addition to the standard library in java there but who'll be the ones making OpenOffic
Re: (Score:2)
[citation needed]
Are you really so unfamiliar with computers that you need a citation for that? Go through the list of Apple products, look at the equivalent open source packages, and you will find that the majority of them are sponsored or paid for by someone, or are done by people as part of their job.
I know it's true for the Linux kernel and probably some other server software, but there's huge amounts of open source that I would be very surprised if someone was getting paid for.
There's also huge amount
There, fixed that for you.... (Score:1)
Recent talk regarding the lack of stability in MSFT's stock price under Steve Ballmer's hand has Slashdot commenter questioning the relative importance of closed-source code. 'Having availability of large assets is a central factor in establishing trust in the business community, as knowledge that the assets are available can often allay fears about the liability of a particular business product. And yet, this trust can often be overstated, the commenter pint out. Members of the business community have been
Think of the children of the parent company... (Score:2)
Re: (Score:2)
Does not. Completely different user base.
Re: (Score:1)
Re: (Score:2)
In contrast to MySQL and OpenSolaris, PostgreSQL is one of the most open communities around. The core members are spread among several companies, it's BSD licensed with no requirement to assign copyright, and the community is made up of a wide variety of people. Not only that, they have established, effective, and written policies for release management, patch review/acceptance, etc.
GPL means never worrying about lifespan (Score:2, Insightful)
If you choose a GPL app for your critical infrastructure, you're pretty safe. If the vendor, sponsor, developers and everybody else involved drops it you can support it yourself until you can migrate to another platform or just become the primary fork. Choosing GPL means never having to say "oops", unless you're the kind of fool that wants to take a GPL app proprietary.
A commercial closed-source app? No, you're maintaining legacy hardware that supports it until you can't get parts on Ebay any more, and
Re: (Score:3, Insightful)
Assuming development continues. If the open source app isn't staying competitive with alternatives then you're in just as bad of straits as being a closed source customer.
I've seen numerous open source projects just completely die. I've seen numerous closed source projects just completely die. Usually unless you're a top 5% company you can't afford to continue development yourself long enough to make any meaningful contribution. It's usually easier to adjust your infrastructure than it is to continue d
Re: (Score:1)
Maybe you need a remedial education in Turing.
Despite what software vendors like Microsoft and Oracle would tell you, bits don't actually rot. Software doesn't age. It's a mathematical construct that works or doesn't. If it worked once then it always will and if it didn't who cares?
Open projects that have no utility are out of scope for my comment. If you use it and you need it, naturally you'll adopt it. And if nobody uses it or would adopt it maybe it's best stored in the archive against future nee
Re: (Score:2)
Re: (Score:2)
Re: (Score:3, Informative)
All non-trivial software nowadays is built with an enormous reliance on some set of shared libraries. As time marches on, those libraries will diverge from the ones the software originally compiled against. Eventually, some API will drift enough that code stops working, and that's where the most difficult to avoid bit rot comes from.
Yes, you can keep code going without rot forever if you can completely freeze the build/deployment environment. But that's rarely practical. Eventually you will need a newer
Re: (Score:2)
Despite what software vendors like Microsoft and Oracle would tell you, bits don't actually rot. Software doesn't age. It's a mathematical construct that works or doesn't. If it worked once then it always will and if it didn't who cares?
Software doesn't age but our competition isn't standing still.
If we were still using 4 year old software we would be less efficient and create less work every day. Being slower. Being more expensive and less profitable would cause us to fall behind. Lots of software today is advancing at an incredible rate. What would have taken an hour a few years ago can now be done 15 minutes. If your software can't keep up then you're wasting money.
Development is expensive so we only spend our own time and money
Forked to death (Score:3, Interesting)
Re: (Score:1)
Re: (Score:2)
ZFS is buggy and unreliable:
http://www.mouldy.org/zfs-the-final-straw [mouldy.org]
http://opensolaris.org/jive/thread.jspa?messageID=473421&tstart=0 [opensolaris.org]
http://mail.opensolaris.org/pipermail/zfs-discuss/2008-January/016042.html [opensolaris.org]
http://forums.freebsd.org/showthread.php?t=7682 [freebsd.org]
http://markmail.org/message/4prch5ydto6nxquf [markmail.org]
I'm interested in Tux3 and (particularly) Hammer though.
http://www.ntecs.de/blog/articles/2008/01/17/zfs-vs-hammerfs/ [ntecs.de]
Re:Forked to death (Score:4, Informative)
First link: author is vague and incorrect; OpenSolaris supports most common onboard SATA controllers. I have personally run it on nVidia MCP55 and above, Intel ICH7 and above, AMD SB600 and above, and OpenSolaris usually support all these very common chipsets/onboard SATA controllers.
Second link: the author is using unsupported dev builds of OpenSolaris.
Third link: the post is 2 years old and evidence suggests unreliable hardware.
Fourth link: the author complains about FreeBSD, not OpenSolaris.
Fifth link: the author concluded corruption was caused by unreliable hardware.
Search for "$NAME_OF_TECHNOLOGY unreliable" and google will always return thousands of results.
Personally I have a rather pleasant experience with ZFS. I have been using it for 3+ years at work and at home on 5-6 machines with about 50 drives total. It has been rock solid so far. And it has saved my life a couple times when drives died.
Lauded by faint criticism (Score:2)
I've been using FreeBSD for several months now, specifically for ZFS. The more I play with it, the more I like it. Of course, if it wasn't for the few years of running Ubuntu, I wouldn't have built up the skillset or the patience to tinker with things until they work,
Re: (Score:2)
It's not the worst horror stories out there. One sysadmin a few years ago discovered that, if you get the right corruption in a ZFS volume, the ZFS driver will cause a kernel panic when trying to mount it. The data's still there and can be recovered, it's just that you can't do it without manually delving into the filesystem and cleaning it up: the ZFS driver wasn't robust enough. This has probably been fixed by now, though.
Re: (Score:2)
ZFS *can* run into problems if it's run on cheap hard disks that try to boost their performance numbers by returning immediately from a cache flush request instead of actually writing the data to the platters first, but that's not a problem with ZFS itself. Most of the issues that I've seen regarding ZFS have been the end result of the storage subsystem not honoring flush semantics, or the result of a RAID co
Re: (Score:1)
Is that it? Isn't there something else OpenSolaris offers that nothing else does? Anything?!
If that's truly the case, then it's already dead and ZFS will soon/eventually get into Linux, if indeed it's actually worth it.
Re: (Score:2)
Linux already supports ZFS via FUSE, but the performance sucks and can't really get much better since it's limited to running in userspace.
Re: (Score:2)
The GPL and CDDL (which ZFS is licensed under) are fundamentally incompatible with each other
That's true at the moment, but the company which just bought ZFS is known to be very active in Linux development, so it wouldn't be too much of a stretch to think that the license might change in the not-too-distant future, especially if Solaris looks to be reaching end-of-life.
Free as in Future (Score:5, Insightful)
There are many reasons why Open Source is good. The availability of developers is only one reason. Even if there seems to be a lack of competent developers ready to take over the project, simply having that potential can mean all the difference. If nothing else, the more eyes on the code, the more likely that bugs can be found and reported. At some point all closed source software will become unmaintained because technology changes, and there is only a finite set of resources. OSS, however, is always available to tinker with, even long after it seems to be worthwhile. As a comparison, think about older cars. They don't have all the bells and whistles, but still have value because they can still be worked on long after their respective companies moved on to newer models.
As a user of OSS, I prefer it even if there is a slightly better closed source alternative. Even though I very rarely look at that actual code, it's nice to know that it is there. It also says a lot about the company when they close up the code. I'm sure that others feel that way too. I don't mind if you sell your product, but I feel that once I buy it, it should be mine to take apart.
Sadly, Microsoft is a great example of how well closed source and good marketing can be. That is why I secretly want that giant to fall. I still think there is an unfortunately large number of people who don't care where their stuff comes from and what the real cost is as long as it works for the short term.
Re:Free as in Future (Score:5, Insightful)
There's a reason for that - the open-source community hasn't been able to successfully present a long term disadvantage to using closed-source tech that people can relate to.
I'm still using Windows because I honestly can't see a long term disadvantage in doing so. By using it I have all the software I could possibly want, guaranteed compatibility with current and future hardware, and so on. I've tried Linux and all I end up with is compromises to tangible things I want to do with my computer. If long term issues become foreseeable with Windows, then I can give it the flick and change to something else.
You HAVE to present to people a tangible long term issue with using closed-source software that they can UNDERSTAND. Geek ideology isn't enough, and if that's all that you've got, then no wonder closed-source tech is still going to dominate.
Re: (Score:1)
If you really using MS products you can't change to something else. If it weren't for open source software, you couldn't switch to OpenOffice.org, you couldn't access files on Windows with a Mac. There were no way that Firefox became a real competitor to IE if the code of Mozilla wasn't opened up.
My tangible long term issue which closed source software is that you never end the upgrade path. Need a new Windows? - You need a faster computer. Need a new Office CD? - You need to buy the latest Office version.
Re: (Score:2)
Yeah you can. When was it ever true that you couldn't? This doesn't even make one lick of sense.
It's true that Mac uses Samba and the OSS NTFS drivers, but if those weren't available and they wanted interopera
Re: (Score:2)
And as for needing a faster computer, well, bloat is increasing just as fast in the OSS world as in the closed source world, unless you limit yourself to simple and old fashioned apps.
I was recently quite pleasantly surprised to discover that this genuinely isn't the case. I've been running Windows 7 Ultimate 64bit on my desktop for a while without a dual boot, since I had only been using my desktop for gaming. A few weeks ago, I found a lot of inspiration to start working on various projects again, so I wiped one of my hard drives and installed Linux on it again. The Ubuntu beta actually, which reminded me why it's a good choice immediately after install, when in GNOME's system tray, I
Re: (Score:2)
If you compare Windows 7 to its predecessor Vista, it's actually the biggest reduction in bloat I think I've ever experienced in an upgrade. :)
Re: (Score:2)
Here's a very significant tangible benefit open-source software gives you: free and easy-to-install upgrades. Of any established product. Also, open-source software doesn't come in 5 different versions (e.g. Home, Studio, Office, Professional, ...), it comes in 1 version, with all the features in it, what one guy smarter than me called "Awesome Edition".
An idea of how ridiculously easy upgrades are: I was working with Ubuntu (Gutsy Gibbon), and a notice popped up in the corner saying "Do you want to upgrade
Re: (Score:2)
Being highly resistant to viruses has nothing to do with it being open source, though.
It has everything to do with Linux being a minority OS. Security through obscurity, really.
OS X is less secure than modern versions of Windows (which is the first platform to get pwned in Pwn2Own, every time? OS X,) yet there's very little malware for it. Why? Because it's also a minority OS.
Re: (Score:2)
No, it has a lot to do with being open source.
The standard example of this: Microsoft IIS is a minority compared to Linux running Apache, yet IIS generally has a worse track record on security.
Some of the reasons why it being open source help are:
- Lots of eyeballs on code means that fewer mistakes last very long.
- When a problem does arise, you have hundreds if not thousands of people capable of doing something about it, and as a result fixes tend to happen in less than 3 days. With a close
Re: (Score:3, Insightful)
Also, open-source software doesn't come in 5 different versions (e.g. Home, Studio, Office, Professional, ...), it comes in 1 version, with all the features in it, what one guy smarter than me called "Awesome Edition".
hmmm..
...
Ubuntu, Slack, Fedora, Suse, Debian, Mandriva, Gentoo,
Re: (Score:2)
Lucky you. Often times distro upgrades are a disaster unless you are on a rolling release distro like Gentoo (which has its own host of problems). As for the versions, uhh, there are half a dozen commonly-used distros and they do actually have different editions, such as a separate server edition, not to mention frequent releases. OSS does not and never has had one edition (and I certainly wouldn't call it "Awesome" since so much of the desktop software is half-working, limited in features or buggy) and
Re: (Score:2)
I agree completely, and I would like to point out one area that open source can make some inroads in: file formats. Many users of closed-source software use applications that store their data in proprietary file formats. While this may not be a serious problem for us
Re: (Score:1)
I think you mean, how well locking in and marketing can be. I personally wouldn't care for MS at all, and would like to use some of their products, if they would use open standards. If I would know that I can safety use their products and can switch to a better alternative.
But because the case with MS is the exact opposite, I try to avoid anything MS related at all cost. OSS is really good and I prefer open source software but a open standards is a little bit more important to the consumer, I think.
Natural selection (Score:3, Insightful)
A telling statement. If enough programmers find the program useful, but in need of improvement, then it is very likely some of them will improve it. If enough non-programmers think that way then they can pay to have it improved. If this doesn't happen then maybe the program wasn't so very important after all.
This is merely natural selection at work, and for the most part the outcome will be as it should be — unlike closed-source products, which live entirely at the whim of their creator.
Re: (Score:2, Insightful)
> unlike closed-source products, which live entirely at the whim of their creator
I find it silly that you believe that there is no form of natural selection which drives the development/maintenance of closed-source products. In most cases, such selection forces exist and are largely economic in nature.
So, no, both open- and closed-source products are subject to natural selection, it's just that the selection forces on them are somewhat different.
Re: (Score:3, Insightful)
In a sense that's true, yes, but the distinction I was trying to make is a finer one. Open source software is directly exposed to competitive pressures. Closed source vendors may be exposed to such pressures too, but closed source software is not — except indirectly through the vendor.
Now I don't want to argue about terminology, but there is a world of di
Re: (Score:2)
No, you misunderstand. I don't doubt that what happened to XP was in Microsoft's selfish interest, given their ability to force-feed the market with its replacement. The point is that it didn't die due to lack of customer interest: it was killed by a fe
Re: (Score:2)
Yep, I heard Microsoft is thinking of killing off Windows and Office because Ballmer wokeup one morning with a sour stomach. Anybody using those products better get with the times and move to open source alternatives now, because it's only a matter of time before Microsoft decides to kill off its product for fun.
Re: (Score:2)
Er, hardly the best of examples. As I mentioned above they did kill off Windows XP, and because of product activation and OEM licensing it won't be long before it is really quite difficult to obtain and use a copy legally, let alone fix any problems that arise. Granted the decision probably had more to do with profits than alimentary secretions, but from a customer point of view it ha
Re: (Score:2)
A telling statement. If enough programmers find the program useful, but in need of improvement, then it is very likely some of them will improve it. If enough non-programmers think that way then they can pay to have it improved. If this doesn't happen then maybe the program wasn't so very important after all.
One of these models is better for the consumer than the other:
Vendors each compete to satisfy demand.
Demand selects from competing vendor bids.
The former is the retail side of the closed source world as it is today, springing to life variations on the theme which then competes with the others.
The later is the contract driven side of the closed source world, springing to life a single solution which often contains the absolute minimum feature set required to satisfy the contract.
While both are used
Re: (Score:2)
We've been in a similar situation. It's gotten to the point where our customers want an integrated Point of Sale with our service. We spent 2007 integrating with other POS's for specific clients, but to integrate with just the top 10 point of sales in our market was going to cost us well over $100k in SDK's and licenses. We looked to Open source and found only one point of sale solution and it had the basics, but lacked a bunch of basics like employee time tracking and required a manger to know XML and s
Re: (Score:2)
I'm curious about the project you forked from. Were they interested in including your code, merging branches, etc.?
Re: (Score:2)
The problem is one of organization... A program can be extremely important to a large number of people, BUT if the user base isn't all looking for an open source option at the same time, there may SEEM
If there is demand for software, it will keep on (Score:2)
but if there isnt demand for it, there will be no use if you allocate numerous paid developers to it.
Re: (Score:2)
While gimp is pretty good (it would certainly take a man year or two to catch up to it), its still like 10 years behind photoshop and even paintshop in most of the meaningful ways. The problem is that the demands being filled is not the same.
The developers of GIMP are fulfilling developer demand. There is no advantage to fulfilling professional or consumer demand, even though there is PLENTY of both.
Re: (Score:2)
thats an important developer culture problem. developers are creating stuff that would appeal to developers, in developer mindset. if we want open source to really take off as a culture, we need to learn how to work for the needs of the common man, without despising it or harboring elitism.
Oracle is continuing Sun's OS strategy (Score:3, Insightful)
I do understand that Solaris technology is excellent, but anybody who counted on Sun maintaining consistent support for it hasn't been paying attention. So if Sun made you happy before, then Oracle should make you happy now; nothing has changed, the strategy spinner is still spinning.
Re: (Score:1)
Re: (Score:2)
If you want it done you need to do it yourself because, the developers don't have resources and the will to full-fill every users desire
Maybe not every users desires. But there has to be a system where people actually using the software full-time are listened to and included in the decision making even if they don't contribute a lick of code. All the features in the world are useless if it's unusable.
Look at the improvement in the Blender foundation thanks to Elephant's Dream and Project Peach. Real professionals using the product on real projects is how you get real feedback on your product. That's no different than how closed sourced
Re: (Score:1, Insightful)
Only if the developers care. They owe no one their work.
And honestly, many of them want just to write the features THEY need. Not everyone else's, no matter how "important" it is to someone else's "usability" rating - although they often are open to doing small changes for other people out of pure kindness. Either way, that won't change. If you don't like things, get some programming done. too, or hire someone.
Re: (Score:3, Insightful)
Screw it, for $700, I'll deal with Adobe's lousy customer service rather than some OSS prima donna.
Re: (Score:3, Insightful)
For $700 you could probably get some attention from most prima donnas. Try that with Adobe, if you can even get connected to someone without a heavy accent and not reading scripted information you can find on the web anyway.
Re: (Score:1)
Re: (Score:2)
I'd really like hell to freeze over and the gimp to get a human usable UI.
Nah, I like it toasty here in Hell. Why can't GIMP get a good UI, 8+bpc support, CMYK etc without first altering the @#$ing weather? 8I
Netpbm changes with the times. (<3 Netpbm! ;D) So why not the GIMP?
Re:What's that I hear? (Score:5, Insightful)
You mean to say that, when working for no reward, they work on the features that suit their interests rather than your interests? How shocking.
Your concept of user requests as something that developers have to ‘escape’ from betrays completely the wrong attitude. Listening to requests is one thing, but actually implementing them may require a large commitment of time and energy that you're not paying for. If you can convince someone to do the work anyway, for whatever reason, then that's great: everyone wins. If not then ‘do it yourself’ is a perfectly reasonable response.
Re: (Score:2)
It is if you have the time, ability, and willingness to do it yourself. Otherwise it's much more efficient to go buy an existing closed source product that actually does what you want. I'm a coder with a couple of decades of experience across a variety of platforms, so I probably *could* hack on an open-source project to get it to do what I want, but rather than waste God-knows how many hours of my time and then be told to go
Re: (Score:2)
I think you're reading rather too much into the 'do it yourself' response. Nobody is forcing you to use Open Source software, so of course you can go and buy Photoshop if it better meets your needs. However if you want specific functionality added to the GIMP then they have every right to decline to do that for you — to suggest otherwise would be absurd. They are simply telling you the harsh reality that if you want it to happen and they don't have the time and/or inclination, then you either have
Re: (Score:2)
Absolutely, and I have zero problems with being told that. It's ludicrous to expect someone else to spend hours of their free time writing code just because I want a particular feature and am not willing to pay for that time. My point was just that the ability to roll your own changes is always trotted out as
Re: (Score:2)
In short, if you're going to hack the code, AND if you're going to lurk for upwards of a decade in order to be recognized by the community as sentient so that you can re-contribute your changes, then you will prefer today's Open Source ecosystem.
If you are on a tight budget and you are willing to bend your processes like taffy around infrastructure that hackers thought would be a good idea years ago and then forgot to cook it all the way through, or support as the code began to age, then you'll eke by on Op
Re: (Score:2)
Prove me wrong.
Re: (Score:2)
The point was not that open source developers should be obligated to implement everything the end users ask for, but rather that open source doesn't work the way people have been claiming for a decade.
Re: (Score:2)
Who has been claiming what exactly for a decade?
If you mean users fixing problems for themselves, or developers implementing suggestions from end users, then these things can and do happen. Frequently. I've experienced it, and so have others in this discussion.
If you mean that this is guaranteed to happen, of course it isn't, but who would be foolish enough to make such a claim (or gullible enough to believe it)?
Re: (Score:2)
Well, of course it matters the degree to which these things are true. You'd also want to see what happens when you get away from the "poster boys" like Linux.
Re: (Score:2)
Fair points, to which the answers are (a) it varies and (b) it varies. Being open source is no guarantee of quality, and if you pick at random then you will spend most of your time in the long tail of unfinished, unsupported code. The solution is simple: use the good and ignore the bad, just as you would with proprietary software. (Easier, in fact,
Re:What's that I hear? (Score:4, Insightful)
And how's that an excuse against "do it yourself"? If you live in a household, not knowing how to wash dishes does not exclude you from the duty. Now you didn't sign a contract which states that you *must* wash dishes regularly. You can hire a dish washing person, or the other household members can be nice to you and wash dishes for you. But if neither are true then complaining whenever other household members ask you to wash dishes is a douchy thing to do.
"Escape from listening to feedback and requests"? The developer has to eat, how will immediately doing what you say get him his next meal? It won't, so he has the right to do whatever he wants with your feedback, including postponing to an indefinite time in the future.
Re:What's that I hear? (Score:4, Funny)
Your analogy is too confusing for me. Let's say you find some code and it doesn't do what you want.. so you ask the people who work on it to add some improvements so it works for you. They ignore your request. So you ask again. They continue to ignore you. You have a big screaming fit and complain that no-one is listening to you and that everyone is unhelpful and you hate them. I think "douche" is too nice a word.
Re: (Score:1)
Even Linus Torvalds himself uses KDE, and encourages others to do the same.
Linus Torvalds is an idiot when it comes to user interfaces. Just look at git.
Re: (Score:2, Insightful)
Re: (Score:3, Informative)
Torvalds has switched to GNOME.
Re: (Score:2)
Re: (Score:2)
The point of this article is that it doesn't matter, because almost every single person fixing bugs, enhancing it, and porting it to other platforms is employed by Oracle, and wouldn't be able to work on a fork. Nobody else is really contributing, so a fork would die quickly.
Re: (Score:2)
The point of this article is that it doesn't matter, because almost every single person fixing bugs, enhancing it, and porting it to other platforms is employed by Oracle, and wouldn't be able to work on a fork. Nobody else is really contributing, so a fork would die quickly.
But what it overlooks is that most of the people who don't work at Oracle, but who could be fixing bugs, enhancing it, and porting it to other platforms, seem to prefer to work on Linux or BSD instead. The problem is not that the community can't support a free OS--the problem is that with several flavors of BSD and hundreds of Linux distros, the community may be starting to reach the limit on the number of free OSes it can support.
Of course, the article is purely speculative--up until now, Sun has been sup
lurkers and outside contributors (Score:2)
That's wisely put.
As I look at the landscape, I'm actually inclined to think that opensolaris is usefully distinct enough from *BSDs, with interesting and rich tools and infrastructure to attract developers from (esp.) the *BSD kernel development communities, if it becomes clear that a clearer cut opportunity to do this exists.
Also, it looks to me as if the internal Solaris devs actually liked having an open process, and valued being open source, and that while a lot of the reasons for keeping the developme
Re: (Score:2)
It's not a question of numbers. If Solaris provides important functionality that other systems don't, then companies will invest in maintaining a FOSS fork. If ZFS, dtrace, and all that are all a bunch of hot air and nobody cares, then it will die.
The nice thing about FOSS is that, unlike corporate decision making, it's democratic and market-oriented.
Re: (Score:2)
Well, if nobody else is really contributing, it tells you that people don't really care, in which case it doesn't matter.
I certainly don't care about Solaris. I still care a little about Java, but I believe IBM and other groups will continue to develop that under FOSS licenses.
Re: (Score:2)