

lolkrinn wrote:the snow leopard of course : he is faster than a poor penguin (you're speaking on land, because under water it will be the gentoo)
anyway, if they fight, the claw & teeth of the snow leopard and his agility vs an old bird will not gave any chance to gentoo.
http://www.ccpo.odu.edu/Research/globec ... gentoo.jpg
http://www.photoethnography.com/blog/im ... rdCubs.jpg (a choose a cubs one, it's cuter)

Dude.Randy Andy wrote:++
and cause it's free.
Open your mind, open your source!
I will never go back to any prison of mind, if i have the choice.
FOSS for ever.
Regards, Andy.

An issue with reliance on Apple's Mac OS X is that it implements a great deal of propietary APIs on top of UNIX and a combination of Apple's licensing agreement and software dependent on those APIs has the effect of marrying you to Apple's platform. If new hardware debuts tomorrow that is superior, you will be able to neither easily nor legally move to it because you cannot use your essential applications on anything other than an Apple system, because they are tied to the OS and the OS is tied to the hardware. Reliance on Apple OS X only software is the equivalent of handcuffing yourself to a ship and throwing the keys overboard.1clue wrote:Dude.Randy Andy wrote:++
and cause it's free.
Open your mind, open your source!
I will never go back to any prison of mind, if i have the choice.
FOSS for ever.
Regards, Andy.
The only real freedom is to have the ability to choose, each time, every time. Free and non-free software can happily coexist, and for most people their experience will be better for it.
Open Source is wonderful because it lets people build what they want, and get what they want without having to justify its marketability. But OS projects are every bit as political or even more so than regular commercial software, and sometimes you just can't submit your fixes back to the main project just because somebody else doesn't like what you did.
If I had ONLY free software I would go nuts. If I had ONLY a mac, I would also go nuts even though a whole lot of OSS is on there. Maintain the balance, dude!
That's only true if you anticipate massively reconfiguring your system after you installed it. Nobody does that in a real business. FWIW, most companies buy hardware, install *software on* it and then leave it that way until it's time to retire it. They run their maintenance, backups and updates, but they design a tool to do a job and then they use it until it's no longer useful. And then they replace it. The old hardware is sold off or scrapped, or MAYBE is turned into some sort of non-critical server. Believe it or not, it's often cheaper to do it that way when you consider that you're paying some guy $60,000 USD a year or better, or even worse you're paying $250 an hour for a consultant to come in and do it. Worst thing of all, using old hardware poses a significant risk of premature hardware failure, and if you don't have a failover you can have 150 people sitting on their thumbs being paid for nothing, and no work getting done so no money coming in to pay for it. All because you wanted to save $1000 by reconfiguring old hardware. The cost of the hardware and the software is minor compared to the money involved in running the business.Shining Arcanine wrote:An issue with reliance on Apple's Mac OS X is that it implements a great deal of propietary APIs on top of UNIX and a combination of Apple's licensing agreement and software dependent on those APIs has the effect of marrying you to Apple's platform. If new hardware debuts tomorrow that is superior, you will be able to neither easily nor legally move to it because you cannot use your essential applications on anything other than an Apple system, because they are tied to the OS and the OS is tied to the hardware. Reliance on Apple OS X only software is the equivalent of handcuffing yourself to a ship and throwing the keys overboard.

huh? Heaps of people include GPL'd software in their proprietary apps. They have to offer up any mods willingly, as well offer up the exact source used, but the above seems to intimate that proprietary apps cannot include any GPL code anywhere, full stop. Which isn't the case. Bundle your ThirdPartySoftware.txt with the installer, and you're done.1clue wrote: especially if you're using even one GNU package in a mountain of other less restrictive software.
The dream behind the license maybe, but the letter of it no1clue wrote:where GNU (maybe I should say RMS/FSF?) tries to keep you from having anything except free software installed on your system, and on any system that computer talks to.
Real world example of "some way" ? Again, all you have to do is share modifications made to a GPL'd app. You don't have to open source your entire project.1clue wrote:If I want to use a piece of Microsoft software in some way that the license terms don't allow, I can at least call Microsoft and tell them the situation, and they might find some way to bill me so it's legal. If you want to use GNU in some way that the license doesn't specifically support, you're just plain out of luck.
Or just include your ThirdPartySoftware.txt.1clue wrote: Better sit down and start writing code to replace it. Or find out if it used to be commercial and go talk to the company who OS'ed it in the first place, see if you can buy a copy of that version.
FUD. Again, nothing in the various permutations of the GPL restricts you from using covered software in conjunction with proprietary software, or software under any other license. It affects only redistribution constraints - which again are pretty much nothing beyond, offer the source of the GPL'd app, offer the source of any modifications made to said GPL'd app.1clue wrote: If you read my previous post, you'll see that I have both a Mac and a Linux box. What I didn't mention is that most of my critical software can run on either. I also didn't mention that one requirement of my job is that my software interfaces and is tested against Microsoft SQL Server and the entire Microsoft business suite, and Business Objects, and Oracle Financials, and JD Edwards. So I also have a couple Microsoft VMware instances on developer licenses for the things I need to test on the fly, and tools to interface with the rest. I not only MUST use non-free software, I MUST use a lot of it. The only way I can change that is by changing my entire career to a completely different industry. My job involves writing software to interface with existing systems. Those systems are almost entirely proprietary. The tools for interfacing with many of them are entirely proprietary.
And now we've fallen way into the realm of the subjective. OS X and I divorced after a month. I spent the better part of the last decade or thereabouts working for a software vendor that produced exclusively Windows software (that had to interface with too many offerings from MS to list - and of the worst non-MS, fuck me Crystal Reports is gobshite...anyway). My transition from Windows to the various Linux DE's and WM's was seamless - no need to re-learn everything, everything was laid out in an intuitive enough fashion that I could pick it up with minimal effort.1clue wrote:You probably wanted it because the UI is the best bar none, right out of the box.

Statically link your proprietary app against any GPL or LGPL code and technically you are forced to release the entire app under a compatible license. I've been participating in GPL compliance audits for Cisco and this is their interpretation of the GPL.cach0rr0 wrote:...
Real world example of "some way" ? Again, all you have to do is share modifications made to a GPL'd app. You don't have to open source your entire project.
...

You need to distribute it outside your organization for that to happen and I suppose that it is possible to fix it by replacing the GPL code with non-GPL code if there is a mistake.John R. Graham wrote:Statically link your proprietary app against any GPL or LGPL code and technically you are forced to release the entire app under a compatible license. I've been participating in GPL compliance audits for Cisco and this is their interpretation of the GPL.cach0rr0 wrote:...
Real world example of "some way" ? Again, all you have to do is share modifications made to a GPL'd app. You don't have to open source your entire project.
...
The insidious part is not the large libraries, which can generally be dynamically linked and, if they are licensed under the LGPL, merely require an acknowledgment, as you stated. No, the dangerous case is the programmer than innocently and ignorantly includes some GPL licensed code within his company's proprietary source code. This triggers one of the so-called viral GPL events where the entire proprietary code base linked with the GPL fragment legally becomes licensed under the GPL.
- John
I don't think that's technically true. Any individual should have the right to redistribute to anyone the source of any software that gets sucked into the GPL even from within an organization and perhaps even under an NDA. I would think that NDAs are fundamentally incompatable with the GPL because it concerns universal individual rights and never those specific to a group.Shining Arcanine wrote:You need to distribute it outside your organization for that to happen
I too tend to take the middle ground - tending towards freedom but there are exceptions. I can largely identify with Stallmanesqe philosophy. Software freedom is important and always a goal, but I think we need to work more on identifying which types of software are especially detrimental to freedom and which are not. Two Adobe examples - Flash and Photoshop. The former is a proprietary reference implementation of a nearly ubiquitous technology with no on-par alternatives. It is ridiculously damaging and it's continued support is dependent upon the commercial interests of a single company with few obligations.1clue wrote:I get seriously bent when people think that extremists are the salvation of mankind.
Completely agree! The notion of restricting freedom in the interest of freedom is laughably absurd.1clue wrote:To bash a distro because they allow use of non-free software is to bite the hand that feeds you.

krinn wrote:Sarah palin, she's friend with gentoos ?Cyker wrote: But... not many people know that the Gentoos are friends with a certain gender-confused super cow who will surely squash the snow leopard flat!
This is a really interesting question. While I'm not certain at all what the technically legal answer is, I can guess that there is a massive amount of internal-only software out there which uses GPL software in ways that would definitely be in violation were it to be released to the public.Ormaaj wrote:I don't think that's technically true. Any individual should have the right to redistribute to anyone the source of any software that gets sucked into the GPL even from within an organization and perhaps even under an NDA. I would think that NDAs are fundamentally incompatable with the GPL because it concerns universal individual rights and never those specific to a group.Shining Arcanine wrote:You need to distribute it outside your organization for that to happen
You'd lose your job for sure but it's still an interesting legal question. I wonder if its ever been tested in court and/or who would win out in a battle between NDA and GPL with regards to software that's exclusively for internal use.
The basic dream that there would always be a choice for any type of software, with a free alternative for any application, is great. In reality though, as you pointed out, not only is there often no FREE alternative, but in some cases there isn't even a commercial one. Flash is and has always been a buggy, poorly written piece of junk with infinite security holes. But it works, and EVERYONE uses it. And there are no seriously competing products.I too tend to take the middle ground - tending towards freedom but there are exceptions. I can largely identify with Stallmanesqe philosophy. Software freedom is important and always a goal, but I think we need to work more on identifying which types of software are especially detrimental to freedom and which are not. Two Adobe examples - Flash and Photoshop. The former is a proprietary reference implementation of a nearly ubiquitous technology with no on-par alternatives. It is ridiculously damaging and it's continued support is dependent upon the commercial interests of a single company with few obligations.1clue wrote:I get seriously bent when people think that extremists are the salvation of mankind.
Photoshop on the other hand, while proprietary and ubiquitous, is not especially harmful. It is a top-level application, not a platform that is depended upon by everyone and everything. It's development doesn't really hamper the development GIMP. It isn't a standard or reference implementation of anything. If Photoshop disappeared tomorrow it would not screw over the entire computer-using populous. I would say that overall the existence of Photoshop does more good than harm, and while it's users accept sacrificing some freedom, they are not necessarily imposing that sacrifice upon others - a very important distinction.
Unfortunately, a lot of the serious, professional-grade, domain-specific, high-level application software missing from the Linux platform is of this second category, and I think people ought to have the freedom to use it if they choose.
Completely agree! The notion of restricting freedom in the interest of freedom is laughably absurd.1clue wrote:To bash a distro because they allow use of non-free software is to bite the hand that feeds you.