Slashdot Mirror
O'Reilly on the Commoditization of Software
Iorek writes "International Data Group/Sverige has a great interview with Tim O'Reilly, CEO of O'Reilly & Associates Inc. From predictions of eBay's purchase of Oracle to discussions of the failings of open source licenses, O'Reilly's certainly not reserved. I couldn't help but be reminded of the rise of this site and slashcode."
The best/greatest standing part about open source isnt GNOME or KDE, or that we all have free speach software, its what we are DOING with that software. Amazon is built on perl, and look what it has accomplished.
Later in the artical he comments on Debian, and how the creator and his company Progeny dont view linux as a product, but "a set of commodity software components he can put together for different purposes."
What he's getting at is that if the OSS community wanted to push forward, you need an idea and then use linux as the tools for that idea, suhc as automated backup, or something snazy like amazon (where it is a tool, and not the product). Trying to market it as a free desktop platform (in which case linux is the product) just wont cut it. I've done projects for my university, and its worked before, and it will work again.
Disclaimer: Do I beleive that linux cant be a product? No, I'm just saying that *ONE OF* (and not limited to) the best ways is to use it as a tool, not a product.
We don't need an "overrated" so much as we need a "you completely missed the parent's point, dumbass..."
I just finished attending a Molecular Biology Training class, and I couldn't help drawing parallels between Open Source and the public Research that is on-going, such as the Human Genome Project.
Like open source software, public research labs publish the data they found, such as mouse or yeast genome, into the public domain (Humor me, I know that Open Source is not public domain, but it's darn close in terms of availability and cost). In addition, when a lab creates a new genomic library, they are supposed to make it available to anyone who asks. Sounds a lot like Open Source.
However, privately funded research usually do not have such policy, and use patents, trade secrets, and Copyrights to protect the IP. This has some effect in slowly down advancement in science in many ways. Such research also lead to imporant, and profitable advances for the companies involved.
But, due to limited public funding, not all worthwhile projects are funded in a timely fashion. A grant request to the NIH may take years before approved. A private company, seizing an oppertunity, may choose to invest and jump start a new field of research.
It seems that both models can co exist, and maybe it's time to have a publicly funded, or even an industry funded, organization, the supports Open Source development. The group should focus on open standards, common tools and platforms, and anything else someone can make a good case for. Something that will advance our knowledge, and make life easier. Something that we all cooperate on, rather than having blackmails or mighty pissing contests.
Maybe we should begin to treat Computer Science like Science, and really advance it methodically, rather than "My code is faster than your code..."
Linux vs Windows was never the proper battle, it was always a battle over what you DO with these things, and how you do them more effieciently than the other guy. Lots of companies NEED something like Exchange, so they by an Active Directory and Windows by default, and so on and so on.
O'Reilly is dead on right. All this shit is just commodity for the applications built upon it that actually generate income. Superiority of one platform over another is a moot point. No one decides to buy a book at Amazon because of Linux, instead of Barnes and Noble because they run on IIS, so get over it.
Windows against Linux is now like Goodyear versus Michelin. Who gives a shit? Only tire makers, not CAR makers. So, it is time to focus on building shit that rides on these things, instead of so much focus on the things themselves. No side has an advantage right now, but that could change overnight. Suppose Microsoft buys Amazon, or EBay buys Oracle? Same players, whole new battle, and all this crap over which OS is better doesnt mean a thing.
What if Microsoft buys Macromedia; takes Flash and does interesting remoting stuff with Web Services tied only to .NET? What is the competing solution from IBM going to look like?
I've got no answers, but I agree with O'Reilly that things are going to get very interesting over the next few years, and things are never going to be the same.
Having read the article twice I'm not qutie sure I get O'Reilly's point.
What he's saying is correct, but it's not exactly earthshattering in anyway. Amazon puts together some services that rock. They patent them. And then they sell the service to others. That just seems logical.
How that ties into driving Open Source I'm not sure. If they're only devleoping proprietary things (services) on top of an open source backbone, they're not really driving Open Source devlopment. Just because I compile my program with gcc or use a perl script doesn't mean I'm driving open source development in anyway. They're just using it as the foundation to build on.
Open Source is by definition controlled by anyone who wants it to be. Maybe I'm missing something here, but it seems like he's just stating the obvious and it has little to do with Open Source.
regarding an open source gui...
,or change it's behavior.. but, in general, it's built to behave a certain way, and you can go around to macs everywhere, and the machine behave the way you expect them to. The developer knows what the user expects, and doesn't have to account for a dozen different ways to interface with things. More importantly, he has somewhre to start.. look how many windows applications have varied interfaces. To really understand this, in case anyone is doubting it, just sit down with a fresh mac and mac user for a few hours and learn how to install software, work with files, etc... you'll get it.
(agree with everything you said, btw)
As a long time hardcore technical guy, and let me back that up by saying I'm a unix nut, I've been using linux heavily for 10 years now, solaris before that, and I get right into the guts.. I like assembly, circuit boards, and whatnot. I like a command prompt and I don't like microsoft.... anyway....
as a hardcore technical guy, open source liker, and a recent convert to OS-X... the comment about a gui got me thinking.
I like open source. I like open everything. I don't like being told what to do with my computer. Yet, I LOVE OSX, and I recognize that the one strength MacOS really has is that apple controls the desktop. It's not that you can't skin it,
So.. we want an open source gui. Here's the thing... the only reason the mac has the "world class gui" feel to it is BECAUSE of a certain lack of openness.. we're talking about a benevolent dictator here. Apple developers know what to expect on the desktop, know how the mac user expects it to behave... and that's the main attraction. If you don't want that, you might as well go use linux.
Yes, we can do stuff in linux that OSX can't do. Yes, open is good, no argument here...I'm just tossing out the thought that, when it comes to providing a rock solid user experience, for a general purpose computer... a lack of choice is sometimes what's needed.. to get people thinking and doing the same thing.
You can sit someone down and show them windows -vs- mac.. and invariably, the mac people get more done, and are more comfortable with their gui.. and it's not because one is more customizable, or more flexible.. in fact it's the opposite.
...Apple. Look at what Apple did with OS X. Apple took an Open Source OS and pinned it up with a proprietary front-end. The system benefits from all of the Open Source advancements in hardware control, while at the same time, the user has all the benefits of a modern, easy-to-use interface.
The FreeBSD folks get some benefit as well. Besides having another big company using their code, testing it (and supplying patches) they kind of avoid the tug of war that part of Linux is going through - the whole "is it for geeks or the masses?" The coders who are good at one tend not to be as good in the other. So the FreeBSD coders can concentrate on the lower level bits, and have the Apple folks worry about getting the real fancy GUI on top of it.