I find it quite handy to be able to have source code snippets in the documentation (even when these "snippets" a long enough to be copyrightable and thus subject to the license), or generate documentation from the source code.
And if you'd bothered to read the quote in the parent post, you might've noticed the quote about not using CC-licenses because they're not compatible with the GPL. So pray tell, why the hypocrisy of advising against using a CC license for documentation (based on not being GPL compatible) when the GFDL isn't GPL compatible either?
Both of those divisions have something in common though. They're both media divisions. It seems to be some sort of natural law that mediacorporations have to become assholes as soon as they pass a certain size. Most independent labels are awesome. All big record companies, movie conglomerates, large game developers, etc. are pissheads.
You know, much as I begrudge Sony for the removal of Other OS, it would be a gross misrepresentation of reality to call Other OS "one of the most important features" (at least without qualifying it with "for a small minority").
They almost certainly had that info on separate systems. Why else the "Billing address, password questions, and credit card info may also have been taken." disclaimer. If the information had been on the same system they would have been sure.
However rather than assume that the information is safe just because it was on a separate server, they're saying that "at the moment we don't know. Please be vigilant until we can give a definite answer".
Actually, I've hacked my Wii to load games from a hard drive. Not only do I only load it with games that I actually own. I haven't even loaded it with all the games that I own, because the *fucking* shitty DVD in the Wii has broken. Glad I did that hack so I can at least use the Wii for something sensible...
(Though to be fair I hardly touch the Wii these days, since I have a PS3 with tons of great titles).
- Android ships every dependent binary in the.apk app file. This eliminates the nightmare of having your app crash because some library you use gets updated.
- Debian is all about reusing.so files across applications. This made sense in the '90s when disk space was scarce, but now days, it's just dumb. The reason it takes years to get a packaged library into Debian Stable is that it takes years before we believe you library wont cause other apps to crash.
Shared libraries still makes just as much sense. Packages that include their own copies of libraries (or for that matter are statically built) are a serious seurity issue. It's mostly fine for applications that can be sandboxed, but mostly it's a security nightmare. A library change that causes applications to crash either indicates incorrect assumptions made in the application (possibly due to a poorly documented library), or an ABI-break in the library -- the latter should always trigger a bumped SO-name.
Part of the reason that it takes a long time for Debian to release is the size of the archives, part of it is because in a lot of cases we do quality assurance on behalf of application writers who believe that embedded library copies is the greatest thing since sliced bread.
Soft links can be cross file system. Hard links cannot (I'm pretty certain this applies for Windows too). The easiest solution using mount (at least on linux) is via bind mounts, where subtrees (or indeed a single file, or using rbind, a subtree and its underlying mounts) of a file system can be mounted in other locations.
WTF? I'd certainly be happy to trade $23,540 with you for a cool billion AUD.
According to XE:
"1,000,000,000.00 AUD = 1,005,998,910.71 USD"
According to google:
"1 billion Australian dollars = 1.0033 billion U.S. dollars"
(This all based on billion being in short scale)
One? Apple has released 4 models of the iPhone by now, TTBOMK.
Besides, I'm fairly sure the comparison is about mobile OS (so it should really say iOS rather than iPhone).
An interesting theory, but most likely incorrect. The reason? Not all save games are copy protected; the developers can choose for themselves whether or not the saves are copy protected. If Sony were afraid that buffer overflows in save games could be used for exploits, they would most probably have enforced copy protection on all save games.
First of all, Aron isn't spell with double-A in Swedish, second of all Andersen is a Norwegian/Danish name (the Swedish counterpart would be Anderson) and again, not spelled with double-A.
Oh, and you've gotta let your imagination run -- remember, there's (almost) the whole Unicode space to choose from:)
Of course, as far as English goes, Z is the end (Zonky Zebra?).
But there's more to poetry than just alliteration. Maybe some neat haiku-based code names?:P
Hmmm, so the btrfsck I have installed on my system is imaginary? On a Debian system the relevant package is btrfs-tools, but you might be running a different distro where it's called something else.
So, to bankrupt Sony and Nintendo I can simply write a script that downloads one game from each company over and over again... After all, if downloads equals loss, enough downloads would bring both companies to their knees. In fact, I'm sure that the entire entertainment industry could be brought to their knees with wget...
Uhm, what do you mean with somewhat slower in general?
There's no overhead of the raster interrupt except when it actually triggers. Sprites steal clock cycles from the rasterlines they cover though.
BTW: Apart from showing sprites in the borders it's also possible to show the content of the "ghost byte" in the upper and lower border.
At least in Sweden and Finland (probably a lot of other countries too) the traffic signals already emit audio signals for red and green (and also "soon to turn red").
320x240 is too small for C64 emulation -- while the text area is only 320x200 (8x8 pixels/character, 40x25 characters), the borders need to fit too, since a *LOT* of software for the 64 uses the border.
A not too wild guess is that this will probably remedied in the wrong way; by adding more IP protection to the fashion industry, rather than following their example.
Slashdot Mirror
I find it quite handy to be able to have source code snippets in the documentation (even when these "snippets" a long enough to be copyrightable and thus subject to the license), or generate documentation from the source code.
And if you'd bothered to read the quote in the parent post, you might've noticed the quote about not using CC-licenses because they're not compatible with the GPL. So pray tell, why the hypocrisy of advising against using a CC license for documentation (based on not being GPL compatible) when the GFDL isn't GPL compatible either?
This is quite ironic, since the GFDL isn't GPL compatible either...
Both of those divisions have something in common though. They're both media divisions. It seems to be some sort of natural law that mediacorporations have to become assholes as soon as they pass a certain size. Most independent labels are awesome. All big record companies, movie conglomerates, large game developers, etc. are pissheads.
You know, much as I begrudge Sony for the removal of Other OS, it would be a gross misrepresentation of reality to call Other OS "one of the most important features" (at least without qualifying it with "for a small minority").
They almost certainly had that info on separate systems. Why else the "Billing address, password questions, and credit card info may also have been taken." disclaimer. If the information had been on the same system they would have been sure. However rather than assume that the information is safe just because it was on a separate server, they're saying that "at the moment we don't know. Please be vigilant until we can give a definite answer".
Still doesn't make any sense though. The PSN store can be closed down without disabling the rest of PSN.
Actually, I've hacked my Wii to load games from a hard drive. Not only do I only load it with games that I actually own. I haven't even loaded it with all the games that I own, because the *fucking* shitty DVD in the Wii has broken. Glad I did that hack so I can at least use the Wii for something sensible... (Though to be fair I hardly touch the Wii these days, since I have a PS3 with tons of great titles).
No, the MAC address is the "unique identification number, of the router" (though there are ways to spoof a MAC address too).
Just posting to revert mistaken moderation :/
Shared libraries still makes just as much sense. Packages that include their own copies of libraries (or for that matter are statically built) are a serious seurity issue. It's mostly fine for applications that can be sandboxed, but mostly it's a security nightmare. A library change that causes applications to crash either indicates incorrect assumptions made in the application (possibly due to a poorly documented library), or an ABI-break in the library -- the latter should always trigger a bumped SO-name.
Part of the reason that it takes a long time for Debian to release is the size of the archives, part of it is because in a lot of cases we do quality assurance on behalf of application writers who believe that embedded library copies is the greatest thing since sliced bread.
Soft links can be cross file system. Hard links cannot (I'm pretty certain this applies for Windows too). The easiest solution using mount (at least on linux) is via bind mounts, where subtrees (or indeed a single file, or using rbind, a subtree and its underlying mounts) of a file system can be mounted in other locations.
WTF? I'd certainly be happy to trade $23,540 with you for a cool billion AUD. According to XE: "1,000,000,000.00 AUD = 1,005,998,910.71 USD" According to google: "1 billion Australian dollars = 1.0033 billion U.S. dollars" (This all based on billion being in short scale)
I didn't include the iPod or iPad; iPhone,iPhone 3G,iPhone 3GS, iPhone 4; four models.
One? Apple has released 4 models of the iPhone by now, TTBOMK. Besides, I'm fairly sure the comparison is about mobile OS (so it should really say iOS rather than iPhone).
It's available on DVD too, so I'd suggest an upgrade :)
An interesting theory, but most likely incorrect. The reason? Not all save games are copy protected; the developers can choose for themselves whether or not the saves are copy protected. If Sony were afraid that buffer overflows in save games could be used for exploits, they would most probably have enforced copy protection on all save games.
First of all, Aron isn't spell with double-A in Swedish, second of all Andersen is a Norwegian/Danish name (the Swedish counterpart would be Anderson) and again, not spelled with double-A. Oh, and you've gotta let your imagination run -- remember, there's (almost) the whole Unicode space to choose from :)
Of course, as far as English goes, Z is the end (Zonky Zebra?).
But there's more to poetry than just alliteration. Maybe some neat haiku-based code names? :P
Hmmm, so the btrfsck I have installed on my system is imaginary? On a Debian system the relevant package is btrfs-tools, but you might be running a different distro where it's called something else.
Encoding the video in WebM would neatly sidestep this issue though.
You mean like http://www.emailvirals.com/data/media/1/bible-warning-label.jpg ?
So, to bankrupt Sony and Nintendo I can simply write a script that downloads one game from each company over and over again... After all, if downloads equals loss, enough downloads would bring both companies to their knees. In fact, I'm sure that the entire entertainment industry could be brought to their knees with wget...
Uhm, what do you mean with somewhat slower in general? There's no overhead of the raster interrupt except when it actually triggers. Sprites steal clock cycles from the rasterlines they cover though. BTW: Apart from showing sprites in the borders it's also possible to show the content of the "ghost byte" in the upper and lower border.
At least in Sweden and Finland (probably a lot of other countries too) the traffic signals already emit audio signals for red and green (and also "soon to turn red").
320x240 is too small for C64 emulation -- while the text area is only 320x200 (8x8 pixels/character, 40x25 characters), the borders need to fit too, since a *LOT* of software for the 64 uses the border.
A not too wild guess is that this will probably remedied in the wrong way; by adding more IP protection to the fashion industry, rather than following their example.