The Future of Closed Source Software and Linux
slashy writes "What is the future of closed source software and Linux? OSWeekly.com delves into the subject and emerges with a possible answer. Quote: "I have been struggling with one major problem lately with the Linux operating system and that problem is the amazing lack of new and exciting software. It's frustrating because by the time said software does finally make its way down to the Linux user, the Windows crowd has been using it for nearly a year or longer.
Perhaps some of this is because there does not appear to be a clear, simple to follow outline cooperative for companies to design for the open source operating system. Arguably this is because of the perceived need to keep things "open," however, I feel it's time for Linux to grow up and find some kind of common ground with the closed source community. I am a firm believer that both parties could learn a lot from each other; unfortunately I don't see that happening any time soon."
"Lack of new exciting software"? Try xgl/compiz! It's the most exciting software I've seen since a windowing environment!
Perhaps some of this is because there does not appear to be a clear, simple to follow outline cooperative for companies to design for the open source operating system. Arguably this is because of the perceived need to keep things "open," however, I feel it's time for Linux to grow up and find some kind of common ground with the closed source community. I am a firm believer that both parties could learn a lot from each other; unfortunately I don't see that happening any time soon."
/. Sorry if you don't like it or don't believe it, but that doesn't make it less true. Or at least, that doesn't it make it less true in the eyes of software developers.
Actually, this is exactly what I have heard from a number of software vendors. I review software and gadgets for a few web sites. One of my testing criteria, particularly for hardware, is if the hardware is Linux-compatible. When it comes to software I always ask if there are any plans to offer a Linux version of the software. The answer that I hear the most often is in regards to a lack of available resources, which I certainly can understand since I review a lot of software form independent companies. But when I question further about asking Linux coders to help with the conversion, the major of companies that have shown an interest in a Linux port say that they've attempted to do so, but the programmers that they approached expect the software to be open-sourced if the company is to get their help. I've even had some developers of software that's geared more towards a particular science admit that they think there would be a huge demand on their software for Linux, but the "requirement" by Linux coders that the software is open-sourced killed the prospect of releasing a Linux version.
As much as I'd like to brush that off as "just an excuse", look at a lot of the replies here on Slashdot about Linux and open-source and you'll quickly see that HE'S RIGHT! I love open-source (or at the very least open standards) just as much as anyone else here and I use it whenever feasible. But there is definitely an assumption among a lot of Linux users that if it's available on Linux the course code has got to be made available or else it doesn't belong on Linux, like it's some kind of plague.
Now, I'll confess that this attitude has been diminishing as Linux eeks its way into the mainstream. The attitude is shifting away from open source and more towards open standards. But there is still a big movement and big preconception that "Linux == Open Source" and "Closed Source != Welcome On Linux".
NOT flaming here, folks. Just relaying what I've been told by software developers and what I've seen here on
Yes, absolutely. You are free to release Linux user applications under any license you choose. Kernel contributions are a different story, but user-applications are completely up to you.
As I said, I'm just relaying what other developers have told me. That's all. Take it at face value.
However, you cannot deny that there it a very strong sense of "Make the source code available!" in the Linux community. I'm NOT saying that it's right or wrong, just that it's there. And don't say that Linux coders do not require open source! I've seen postings on Slashdot and other Linux communities that have actually criticized companies for releasing software on Linux but not making their source code available as though it's some kind of expectation! I know enough to take such postings with a grain of salt, knowing that there are extremists in every crowd who will never be satisfied, but what the hell do you expect a developer to think if they had plans on releasing their software but then saw that there's an expectation of releasing their source code?
It's called Konqueror. It has these wonderful things called 'ioslaves' which can be accessed by special 'protocols'. Not only does it support browsing the local filesystem and the web, but also ftp sites (ftp://ftp.gnu.org), secure ftp (sftp://blah), info and man page viewing (info:/libc, man:/fstab), and a whole host of other resources. And it presents a unified and self-consistent interface to all of them.
There are fantastic GUI clients for FTP on Linux, and sometimes you don't realize you're already using one on a day to day basis (assuming you're a KDE user).
Pirate Party UK