Last Word on ADTI Document
kris writes "Linux and Main's Anthony Awtrey put together a very nice analysis of the ADTI "Opening the Open Source Debate" paper before and after the temporary retraction. He came up with some interesting research of just why the paper adressed specific examples such as the FAA and exposes the FUD behind the FUD in the paper."
I am unclear on the context. Where was the article he is commenting on, and who was the intended audience?
Other than me not being clear on that, it was a good article once I got through some rough parts at the beginning. I think this guy should write his own paper on the topic, since he seems to know it and took quite a bit of effort to comment on someone else's.
Can someone clue me in to the context? Should I know the names of the people involved? I don't.
Must be a slow Sunday.
-Pete
Soccer Goal Plans
The author of this rebuttal made an excellent point: software in the Open Source is becoming "mature", not only for server applications but also on the desktop. It does not matter that these products will likely never measure up to the level of proprietary versions of software: once the software is "good enough", it will be adopted by more and more people because it is unencumbered by restrictive and expensive licencing.
It may take awhile longer, but it will happen. Of course, the goal of the proponents of the FUD are hoping to head off this inevitability by legislating Open Source software out of legal existance. To be honest, I think that this really is the only course available to them: Microsoft is going to be in huge trouble (sooner than one may think) if they don't stem the Open Source tide.
Look at the tomato! Isn't it sad? He can't dance! Poor tomato!
If a software developer makes an application for a customer that contains GPLed code is it considered "distribution" when he delivers the finished product to the customer?
The Article says:
It seems to me that the statement from the article about would conflict Section 3b of the GPL that says if the act of delivering the finished product to the customer constitutes "distribution."
Could someone more knowledgeable about the GPL please enlighten me sbout this?
There's one more thing about the GPL that most people miss. It is directed to a licensee, not the author. Note from section 7: "Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice."
Prediction:
Open Source dominates infrastructure,
Closed Source handles specific markets, where economies of scale are scarce or specific requirements (e.g. performance) dominate.
Our beloved polar opposites, BillyG and RMS, remain the stuff of fond
Maybe Open Source development turns into a journeyman scene,
where you have to pay some dues and contribute to the general welfare prior
to being hired by a 'serious' company with that fat salary. Such an ecosystem might lead to more useful software. Or not.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
I want a document that has the 10-20 most often heard arguments representing the FUD companies try to spread about Open Source in general and the GPL in particular, and a clear, concise, relevant, non-inflammatory rebuttal to each.
The author's language, such as "the market is a tough bitch" and "hell yes!" will not fly if I ever want to supply a rebuttal to these kinds of arguments.
Take the original paper's example of "a piece of software an engineer writes that represents 5000 hours worth of work, but uses a GPL component that represents 100 hours of effort. Is the GPL'ed component's requirement to release the original work under the GPL 'fair'?"
The proper rebuttal to this is:
Imagine that an engineer writes a piece of software representing 5000 hours worth of work, but uses a PROPRIETARY component that represents 100 hours worth of effort. That proprietary component has a license that says 'the engineer will pay $10,000, plus some percercentage of revenue the original work generates". There are PLENTY of proprietary products like that. Is that fair?
It is up to the engineer to decide. If his time-to-market is so critical that those 100 hours are worth $10,000 plus a percentage, then that engineer will do it... otherwise, they will just write it. It is a business decision, like any other.
In both cases, the person who wrote the 100 hour effort component OWN THAT WORK, and get to say what the costs of its use will be. The person using it has to decide what costs they are willing to pay.
In GPL, the cost is not financial (at least, not directly). The 'cost' is to release the 'new' product under the same license. Many other licenses (both Open and Proprietary) put 'costs' on that have nothing to do with monetary value.
I want to see 10-20 arguments like this made. they are clear, concise, NON-INFLAMMATORY, and make a point.
- http://www.adti.net/html_files/technology/ander
s on ad_techtrends020501.html - http://www.adti.net/html_files/technology/purps
q ui rrel_familiarity0201.html - http://www.adti.net/html_files/technology/Westo
n _c ounty_gazette_041901.html - http://www.adti.net/html_files/technology/Stand
a rd _examiner_techtrends041001.html
And so on... Just click through the stories that are ALL pro-Microsoft, anti-Antitrust. Holy Cow. Western Civilization depends on an unfettered Microsoft to lead the technology charge!-- @rjamestaylor on Ello
Why? If you work with non-expert mainstream users, as I do on a daily basis, you'll find out that they care not one iota about the OS. They are completely invested in their stored data and their time investment in learning how to use their current set of apps. If you want them to move to a different OS it has to have not a set of virtually identical apps, but the ability to use all of their existing docs in a truly seamless fashion. And even that's not enough to get them to switch. Non-expert mainstreamers, almost without exception, hate PC's, and consider them too hard to use. Asking them to undertake the task of relearning a lot of stuff for what they'll see as no net gain in functionality or convenience is a non-starter.
Until Linux can overcome all those hurdles, it's a Windows world. I hate it every bit as much as does anyone else on /. reading this, but that's the way it is.
In one place, ADTI claimed I said something I didn't say, and in others ADTI intentionally carefully quotes only part of what I said.
- David A. Wheeler (see my Secure Programming HOWTO)