Windows is broken Like the first Windows Bluescreen has spoken Like the first crash. Praise for the crashing, Praise for the breaking, Praise them for springing fresh from install.
Usually the CVS of Open Source projects is not writable by everyone. As non-maintainer, you'll send in a patch, and the project maintainers review that patch and either accept or reject it. If you cannot convince the maintainers to accept the patch, you won't get it into the code. You can of course fork the code and put your patch in your fork, but that doesn't affect the quality of the original code, for better or worse.
I guess an equivalent strategy for Wikipedia would be to lock the article pages, and let people write proposed changes to the discussion pages only. Then the admins could review those changes and put the good ones into the article.
Copyright also covers derived works. That is, if you create derived works, you must have to have a license to distribute those as well. After all, that's part of how the GPL works: If you create and distribute a derivative work, it demands that you put that derivative work under GPL as well. It couldn't do so if derived works weren't covered (well, it actually cold demand, but you could just laugh at it and otherwise ignore it if derived works were not covered by copyright).
There are some exceptions for fair use, but otherwise, derived works are covered as well. Of course, in addition you get your own copyright on the derived work you produced, which means that it cannot be distributed without your consent as well. IOW: Copyright combine is a subtractive way.
Therefore all four of your scenarios would be copyright infringement (provided the original work was copyrighted).
would anything M$ would do or think of surprise any of us anymore?
Yes. If MS would release Windows under the GPL, I'd honestly be surprised. Not that I'd expect that... but then, if I'd expect it, I'd not be surprised if it happened!
Are you sure? I admit I've not RTFA, but if this poisoning causes you to get different content than you expected, then I imagine it could be a great tool for black hats to insert backdoors into downloaded Linux distributions. You e.g. expect to download a genuine Debian torrent, while you actually download a modified Debian with backdoor.
To get a significant planetary wiplash it would have to be severed several hundred or thousand miles up (i.e. in space). Then you're talking about terrorist nukes or a cometary or asteroidal impact. If something made a Stalk wiplash, my money'd be on the terrorist nuke.
I think the problem with your suggestion is stability: If you are walking on the bottom inside the ball, gravity will make sure that you keep in the middle and the ball rotates to achieve that. If you are on top of the ball, gravity will have the opposite effect.
whether it really is a breach of copyright still isn't clear imho, hence the lawsuit.
So you think there cannot be a lawsuit if you clearly break the law? Hey, I didn't know that. I always thought if you are found breaking the law, you get sued. So the main fault of all those law-breakers is not that they break the law, but that they deny doing so, because if they would make it clear that they break the law they'd be safe.:-)
RFID passports, RealID cards and credit cards. What's next RFID birth certificates and social security cards?
To prevent physical stealing of personal RFID cards, you'll get an RFID chip implanted in your forehead. Which means that you can pay by banging your head against the cash desk.
There's no simple, universally agreed-upon standard for which genes are good
Indeed, even for genetic deceases, things are not always so clear-cut. For example I've heared that in malaria regions there's an increased number of sickle cell anemia cases as well. Why? Well, you'll get sickle cell anemia only if you have two defect genes (i.e. got one both from your father and your mother). If you got only one, you don't get sickle cell anemia, but you get an increased resistance against malaria. And obviously in malaria regions the extra resistance against malaria is a large enough evolutionary advantage to overcompensate for the sickle cell anemia risk.
The last time I tried it I could go more than 30 minutes on Write without it freezing on me for some reason.
When was that. I use it (although not heavily) and I have not had those problems.
I didn't know that more than 30 minutes without freezing would be a problem. Maybe the OOo developers can address your special need with an additional option in the preferences: "freeze every 30 minutes" (the interval could probably be configurable, too).
Let me see if I get this right. If you use these libraries to develop free software you pay no money. If you use them develop proprietory software you pay money. In other words, you make money they make money, if you make no money they make no money. So what exactly is the problem again?
You got it wrong. If you develop GPLed Free Software, you pay no money. If you develop proprietary software (no matter if it is Freeware [i.e. free as in beer] or if you sell it) you have to pay. But if you want to develop Free/Open Source software under a GPL-incompatible OSS license, you're out of luck.
Now why does it matter for Qt/KDE, but not for, say, GIMP? Well, simple: KDE is infrastructure. It's in a similar position as the C library or the gcc runtime library (which even the FSF makes sure can be used for non-GPLed software alike without any problems). Every program which is intended to fit seamlessly into the KDE system basically has to link Qt. And thus you effectively lose the freedom of chosing your license for your code. The situation is different for GIMP: There's generally no need for a graphics program to directly interact with GIMP. Unless you explicitly want to change or add to GIMP, you need not be interested in the GIMP license. Normal code just isn't affected. But if KDE should become the standard desktop, you'll very much be forced to use Qt for your GUI programs (or your program will just not integrate nicely). That's why the standards here are different than from ordinary code.
I don't know how much the MySQL licensing affects other code. Can you write code using MySQL without being bound by the GPL (except by buying a proprietary license, of course)? If not, how standard is the interface (i.e. can you easily write code which would without change work e.g. on both MySQL and PostgreSQL)? If the answers to both questions are "No", then it's effectively a vendor lock-in as well, because again, a database is critical infrastructure for certain applications.
Or how millions of people starved because they couldn't grow their own food because they couldn't just use their grown wheat for the next seed (it wouldn't grow) and couldn't afford new one? DRM isn't just a software/hardware problem. "DRMed" plants are already common in genetically manipulated food. Only that the effects can be more desastrous, because it's about food, which we need, not movies, which we could go without. (OK, technically it's not DRM, because the restrictions are not controlled digitally, but genetically)
More importantly, they'll lose money due to people just not buying their stuff because of exactly those restrictions. I didn't modify my DVD player, nor do I plan to. However I'm not going to buy a player which has to be connected to the internet just to play local media.
Slashdot Mirror
Note that your program isn't valid C either, since in C all external identifiers starting with str are reserved to the implementation (see section "Implementation specific and future problems" in the linked page).
Windows is broken
Like the first Windows
Bluescreen has spoken
Like the first crash.
Praise for the crashing,
Praise for the breaking,
Praise them for springing
fresh from install.
SCNR
Usually the CVS of Open Source projects is not writable by everyone. As non-maintainer, you'll send in a patch, and the project maintainers review that patch and either accept or reject it. If you cannot convince the maintainers to accept the patch, you won't get it into the code. You can of course fork the code and put your patch in your fork, but that doesn't affect the quality of the original code, for better or worse.
I guess an equivalent strategy for Wikipedia would be to lock the article pages, and let people write proposed changes to the discussion pages only. Then the admins could review those changes and put the good ones into the article.
Copyright also covers derived works. That is, if you create derived works, you must have to have a license to distribute those as well.
After all, that's part of how the GPL works: If you create and distribute a derivative work, it demands that you put that derivative work under GPL as well. It couldn't do so if derived works weren't covered (well, it actually cold demand, but you could just laugh at it and otherwise ignore it if derived works were not covered by copyright).
There are some exceptions for fair use, but otherwise, derived works are covered as well. Of course, in addition you get your own copyright on the derived work you produced, which means that it cannot be distributed without your consent as well. IOW: Copyright combine is a subtractive way.
Therefore all four of your scenarios would be copyright infringement (provided the original work was copyrighted).
IANAL however.
Yes. If MS would release Windows under the GPL, I'd honestly be surprised. Not that I'd expect that
Are you sure? I admit I've not RTFA, but if this poisoning causes you to get different content than you expected, then I imagine it could be a great tool for black hats to insert backdoors into downloaded Linux distributions. You e.g. expect to download a genuine Debian torrent, while you actually download a modified Debian with backdoor.
What, Saddam didn't create the Porsche 911?
Well the "no one has ever heared of it" part is what marketing departments are about.
What about space debris?
I think the problem with your suggestion is stability: If you are walking on the bottom inside the ball, gravity will make sure that you keep in the middle and the ball rotates to achieve that. If you are on top of the ball, gravity will have the opposite effect.
I strongly doubt it'll be finished in 15 days.
You got it the wrong way:
In Korea, only old viruses infect browser binaries.
So you think there cannot be a lawsuit if you clearly break the law? Hey, I didn't know that. I always thought if you are found breaking the law, you get sued. So the main fault of all those law-breakers is not that they break the law, but that they deny doing so, because if they would make it clear that they break the law they'd be safe.
To prevent physical stealing of personal RFID cards, you'll get an RFID chip implanted in your forehead. Which means that you can pay by banging your head against the cash desk.
Indeed, even for genetic deceases, things are not always so clear-cut. For example I've heared that in malaria regions there's an increased number of sickle cell anemia cases as well. Why? Well, you'll get sickle cell anemia only if you have two defect genes (i.e. got one both from your father and your mother). If you got only one, you don't get sickle cell anemia, but you get an increased resistance against malaria. And obviously in malaria regions the extra resistance against malaria is a large enough evolutionary advantage to overcompensate for the sickle cell anemia risk.
If you want to be on the safe side, buy the all-blank keyboard and then wear the legends off of it.
Well, then what is it you were typing your post with?
I didn't know that more than 30 minutes without freezing would be a problem. Maybe the OOo developers can address your special need with an additional option in the preferences: "freeze every 30 minutes" (the interval could probably be configurable, too).
SCNR
You got it wrong. If you develop GPLed Free Software, you pay no money. If you develop proprietary software (no matter if it is Freeware [i.e. free as in beer] or if you sell it) you have to pay. But if you want to develop Free/Open Source software under a GPL-incompatible OSS license, you're out of luck.
Now why does it matter for Qt/KDE, but not for, say, GIMP? Well, simple: KDE is infrastructure. It's in a similar position as the C library or the gcc runtime library (which even the FSF makes sure can be used for non-GPLed software alike without any problems). Every program which is intended to fit seamlessly into the KDE system basically has to link Qt. And thus you effectively lose the freedom of chosing your license for your code. The situation is different for GIMP: There's generally no need for a graphics program to directly interact with GIMP. Unless you explicitly want to change or add to GIMP, you need not be interested in the GIMP license. Normal code just isn't affected. But if KDE should become the standard desktop, you'll very much be forced to use Qt for your GUI programs (or your program will just not integrate nicely). That's why the standards here are different than from ordinary code.
I don't know how much the MySQL licensing affects other code. Can you write code using MySQL without being bound by the GPL (except by buying a proprietary license, of course)? If not, how standard is the interface (i.e. can you easily write code which would without change work e.g. on both MySQL and PostgreSQL)? If the answers to both questions are "No", then it's effectively a vendor lock-in as well, because again, a database is critical infrastructure for certain applications.
Or how millions of people starved because they couldn't grow their own food because they couldn't just use their grown wheat for the next seed (it wouldn't grow) and couldn't afford new one?
DRM isn't just a software/hardware problem. "DRMed" plants are already common in genetically manipulated food. Only that the effects can be more desastrous, because it's about food, which we need, not movies, which we could go without.
(OK, technically it's not DRM, because the restrictions are not controlled digitally, but genetically)
More importantly, they'll lose money due to people just not buying their stuff because of exactly those restrictions.
I didn't modify my DVD player, nor do I plan to. However I'm not going to buy a player which has to be connected to the internet just to play local media.
Did you read the subject line? :-)
And have you ever thought about why the dinos died out?
How do you attach a
If you do your image/chart in SVG (or any other XML based format), the XML standard itself should take care of it, shouldn't it?
Any hints of previous plans to switch to OOo in New Orleans?