By the time I had read the subject line's *spoilers* tag, my peripheral vision had read and processed the the first sentence of the parent. I don't think this needs to be modded into oblivion, but it SHOULD require deliberate action from the user to appear.
...as it is known to be physically impossible to copy something down to the atomic level without destroying the original.
The things you learn on Wikipedia:)
The thing is, Linus knows exactly what loopholes the GPLv3 is closing, and he doesn't consider them to be bad things. And in a way, he's got a point. Tivo's video-processing code can still be used in other applications, after all. Isn't that free enough? Furthermore, doesn't the GPLv3 prohibit *anybody* from writing GPLv3 code that runs on a Tivo, even if they weren't the ones who locked the hardware down in the first place?
I think that, from the point of view of the FSF, the GPLv3 makes a lot of sense. But Linus doesn't seem to feel that a lot of the FSF's problems really *are* problems. It's the GPL vs BSD thing all over again, and the question of how much specific freedom you restrict in order to ensure overall freedom, and just because Linus sees the question a different way doesn't necessarily make him right or wrong.
Turns out, though, according to a recent leak from a gaming mag... there IS a moral dilemma in this game. That is to say, you only get the good ending if, counter to all expectations, you play the game relatively honorably.
Just something that I thought deserved mentioning in the whole "is this game REALLY art?" debate.
Now, I'll admit it. I've never gotten to 60. But that's because I barely play at all. Casual players can, in a few months of play (that is, about $90 of subscription fees), make it to level 58, where you can get into Outland. And from what I've heard, it's incredibly fun from there on out thanks to BC.
I don't think the notion of a fork is all that erroneous.
WALTHAM, Mass.--04 Dec 2006--Novell today announced that the Novell® edition of the OpenOffice.org office productivity suite will now support the Office Open XML format, increasing interoperability between OpenOffice.org and the next generation of Microsoft Office. Novell is cooperating with Microsoft and others on a project to create bi-directional open source translators for word processing, spreadsheets and presentations between OpenOffice.org and Microsoft Office, with the word processing translator to be available first, by the end of January 2007. The translators to Novell's OpenOffice.org product. Novell will release the code to integrate the Open XML format into its product as open source and submit it for inclusion in the OpenOffice.org project. As a result, end users will be able to more easily share files between Microsoft Office and OpenOffice.org, as documents will better maintain consistent formats, formulas and style templates across the two office productivity suites.
My worry here is that the add-on itself would be closed-source, and the GPL code would simply be a compatibility layer necessary to run and use the add-on. With that in place the two companies could concievably set up a situation where the mainline OpenOffice sources are playing catch-up with add-on updates that require new pieces of source code to actually use in the standard.Org offering, especially if that compatibility code becomes tangled up in some other feature that OOo is unwilling or unable (due to more obvious and legit patent issues) to make a part of the "real" releases. In other words, it's all legal and GPL-OK, but there's little hope for any OpenOffice other than Novell's actually being able to open the latest version at any point in time.
That's the point where embrace/extend comes into play. Once everyone on open-source is using NOO instead of OOo, Microsoft and Novell can start adding a tweak here, an improvement there, maybe the occasional formatting bug...
Eh, maybe it's farfetched but I can't help but think about it.
The comments made by this teacher were totally inappropriate and took advantage of his authority position. So why not call them that instead of using phrases like "anti-scientific" that imply a war between religion and science?
Does anyone else see this as an incredible boost to projects like Wine and ReactOS? Given that up until now they've had to use Chinese Walls and so forth to figure these things out, it seems to me that this court order is going to save them a *lot* of effort.
I agree on the benchmark thing... it's just.NET's benchmark agreement and not a big deal. The other stuff (virtualization, Defender, DRM stuff) is serious, though, and doesn't deserve the FUD tag.
Slashdot Mirror
By the time I had read the subject line's *spoilers* tag, my peripheral vision had read and processed the the first sentence of the parent. I don't think this needs to be modded into oblivion, but it SHOULD require deliberate action from the user to appear.
Why in the heck was this rated "Troll", anyway? It's a sincere comment. *confused*
...as it is known to be physically impossible to copy something down to the atomic level without destroying the original. The things you learn on Wikipedia :)
Do you know what this means?! *goes to program a cube-based time machine in LISP*
Welcome to Slashdot! Would you like to be a moderator?
Too bad.
Argument #1 is a pretty good one. As for point #2, sed s/write/distribute/g... but I'll go and actually read the GPLv3 anyway ^_^
The thing is, Linus knows exactly what loopholes the GPLv3 is closing, and he doesn't consider them to be bad things. And in a way, he's got a point. Tivo's video-processing code can still be used in other applications, after all. Isn't that free enough? Furthermore, doesn't the GPLv3 prohibit *anybody* from writing GPLv3 code that runs on a Tivo, even if they weren't the ones who locked the hardware down in the first place? I think that, from the point of view of the FSF, the GPLv3 makes a lot of sense. But Linus doesn't seem to feel that a lot of the FSF's problems really *are* problems. It's the GPL vs BSD thing all over again, and the question of how much specific freedom you restrict in order to ensure overall freedom, and just because Linus sees the question a different way doesn't necessarily make him right or wrong.
They're crank-powered. Totally clean, renewable energy! Well, unless you count the methane emmissions from rice-and-beans diets ;)
Doesn't the Zune *already* have video squirt support? And if not, what in tarnation was Microsoft thinking?
Turns out, though, according to a recent leak from a gaming mag... there IS a moral dilemma in this game. That is to say, you only get the good ending if, counter to all expectations, you play the game relatively honorably. Just something that I thought deserved mentioning in the whole "is this game REALLY art?" debate.
The World Health Organization would like a word with your pastor outside.
Now, I'll admit it. I've never gotten to 60. But that's because I barely play at all. Casual players can, in a few months of play (that is, about $90 of subscription fees), make it to level 58, where you can get into Outland. And from what I've heard, it's incredibly fun from there on out thanks to BC.
Well, the registration requirements will need a little tweaking. Becoming an IEEE member requires all of 40 bucks and a Bachelor's degree. :/
I've been saying this for about five years now. Pokémon would make a fantastic MMO.
I wasn't aware that Solaris was really that popular.
You would get to keep them all for yourself, and the orphanage would cry forever.
My worry here is that the add-on itself would be closed-source, and the GPL code would simply be a compatibility layer necessary to run and use the add-on. With that in place the two companies could concievably set up a situation where the mainline OpenOffice sources are playing catch-up with add-on updates that require new pieces of source code to actually use in the standard .Org offering, especially if that compatibility code becomes tangled up in some other feature that OOo is unwilling or unable (due to more obvious and legit patent issues) to make a part of the "real" releases. In other words, it's all legal and GPL-OK, but there's little hope for any OpenOffice other than Novell's actually being able to open the latest version at any point in time.
That's the point where embrace/extend comes into play. Once everyone on open-source is using NOO instead of OOo, Microsoft and Novell can start adding a tweak here, an improvement there, maybe the occasional formatting bug...
Eh, maybe it's farfetched but I can't help but think about it.
Does this look like Microsoft back to its old "embrace and extend" tricks to anyone else?
Sorry... should have RdTFA
The comments made by this teacher were totally inappropriate and took advantage of his authority position. So why not call them that instead of using phrases like "anti-scientific" that imply a war between religion and science?
Translation of the story was sorely needed, and here it is.
Does anyone else see this as an incredible boost to projects like Wine and ReactOS? Given that up until now they've had to use Chinese Walls and so forth to figure these things out, it seems to me that this court order is going to save them a *lot* of effort.
I agree on the benchmark thing... it's just .NET's benchmark agreement and not a big deal. The other stuff (virtualization, Defender, DRM stuff) is serious, though, and doesn't deserve the FUD tag.
Relevant wikipedia article here.
Has anyone else noticed that whenever the editors want an action to appear sinister, their first instinct is to describe it as being done "quietly"?