You're looking too far ahead. The bleeding edge basically has to be this way to hammer out the problems before proposing the standard. On the other hand quite a few new/interesting/exciting/annoying technologies have been drafted together and implemented across the board. Or are things moving so fast that stuff like canvas, that is barely starting to see production adoption, doesn't qualify anymore?
TL;DR It only seems like The Browser Wars because it's easy to pick out the incompatibilities.
No, looks like I got tangled up. Sorry about that. If somone with modpoints can be bothered to nuke my other post from orbit please go ahead. Everyone else, ignore it.
Sure, as long as the company is willing to silently pony up the statutory damages for copyright infringment the BusyBox people should be silent. For some odd reason they want to settle though...
Public domain code doesn't make a statement, public domain code just hands over the code. Copyleft actually works: you can have your draconic copyright (the notion that one either supports copyright as it currenlty exists or is against it in principle is a false dillema), but you will have to write your own code. Subverting rules is much better than just being subverted by them.
True but what other reasons are there to rewrite? Sony isn't OpenBSD, they aren't doing it for ideological reasons. I think part of it might be that posting source code for a single part of a system that comonly involves a bunch of others that theoretically should be there as well invites unwelcome scrutiny.
I think the arguements are more along the lines of: 'is it really usefull to "force" Sony to do this' and 'we shouldn't be vigilant about enforcing the GPL'.
Now imagine doing nothing but castrating 16 hours (or more) at a time for years. For them it's not a "when they do the same thing over and over", doing the same thing over and over is all they do.
Unlikely that he was permitted to talk? Unlikely that he didn't work 35 hour shifts? Unlikely WHAT? What's likely is that you are making wrong assumptions.
I bet you had the "luxury" of talking to your fellow coworkers and maybe, maybe even some protective gear. You certainly weren't guaranteed to fuck up your hands by doing the same exact thing over, and over, and over, and over, and over, and over, and over. Though I do conceede that your bed might have resembled a coffin as well...
Considering that some people have been bitching about memory usage basically since before 1.0, it's safe to say that that couldn't be the reason to lose anything Firefox used to have.
You are free to the country. Ergo, you are there voluntarely your lack of viable choices nothwitstanding. So politics and law enforcment don't enter into anything until they stop you from leaving.
Ever try to use part of a disk for Timemachine? I'd also ask if you've ever lost documents in iWork, but Apple recently came out with the unprecedented invention of autosave, so I won't.
So the same design isn't the same design if you put a stand behind it? Sounds like "on the internet" patents all over again. We did the same design as Samsung, but on a tablet! They totally shouldn't be able to reuse design elements of their non-tablets because we used them in our tablet first...
Slashdot Mirror
Not making your shit available on the other hand precludes you from public sympathy when you complain that you lose money by not selling it.
You're looking too far ahead. The bleeding edge basically has to be this way to hammer out the problems before proposing the standard. On the other hand quite a few new/interesting/exciting/annoying technologies have been drafted together and implemented across the board. Or are things moving so fast that stuff like canvas, that is barely starting to see production adoption, doesn't qualify anymore?
TL;DR It only seems like The Browser Wars because it's easy to pick out the incompatibilities.
No, looks like I got tangled up. Sorry about that. If somone with modpoints can be bothered to nuke my other post from orbit please go ahead. Everyone else, ignore it.
He should be nervous, he is receiving bad legal advice.
The GPL dictates the amount of system memory now?
You mean: "you might be techinically in the wrong but as long as it's not with those BusyBodies no one should criticize".
Sure, as long as the company is willing to silently pony up the statutory damages for copyright infringment the BusyBox people should be silent. For some odd reason they want to settle though...
Public domain code doesn't make a statement, public domain code just hands over the code. Copyleft actually works: you can have your draconic copyright (the notion that one either supports copyright as it currenlty exists or is against it in principle is a false dillema), but you will have to write your own code. Subverting rules is much better than just being subverted by them.
True but what other reasons are there to rewrite? Sony isn't OpenBSD, they aren't doing it for ideological reasons. I think part of it might be that posting source code for a single part of a system that comonly involves a bunch of others that theoretically should be there as well invites unwelcome scrutiny.
I think the arguements are more along the lines of: 'is it really usefull to "force" Sony to do this' and 'we shouldn't be vigilant about enforcing the GPL'.
Now imagine doing nothing but castrating 16 hours (or more) at a time for years. For them it's not a "when they do the same thing over and over", doing the same thing over and over is all they do.
Unlikely that he was permitted to talk? Unlikely that he didn't work 35 hour shifts? Unlikely WHAT? What's likely is that you are making wrong assumptions.
Depends, is that woodworking plant you go to after you get your hand crushed producing for the domestic market?
I bet you had the "luxury" of talking to your fellow coworkers and maybe, maybe even some protective gear. You certainly weren't guaranteed to fuck up your hands by doing the same exact thing over, and over, and over, and over, and over, and over, and over. Though I do conceede that your bed might have resembled a coffin as well...
Internal changes in a dot version? Your versioning system is actively broken, at least theirs doesn't pretend to be meaningful.
Considering that some people have been bitching about memory usage basically since before 1.0, it's safe to say that that couldn't be the reason to lose anything Firefox used to have.
It's not as easy as it should be either. Remind me, how does one recover from a power failure in iWork '09 again?
Of course you have. You have accepted it so far, no?
False choice or false choice. Pick three.
You are free to the country. Ergo, you are there voluntarely your lack of viable choices nothwitstanding. So politics and law enforcment don't enter into anything until they stop you from leaving.
Relevant.
Ever try to use part of a disk for Timemachine? I'd also ask if you've ever lost documents in iWork, but Apple recently came out with the unprecedented invention of autosave, so I won't.
Pagerank was pretty unique actually.
So the same design isn't the same design if you put a stand behind it? Sounds like "on the internet" patents all over again. We did the same design as Samsung, but on a tablet! They totally shouldn't be able to reuse design elements of their non-tablets because we used them in our tablet first...