This legislation is already in place in the UK, leading Ross Anderson to conclude that he is an international terrorist (though not for economic reasons).
Can you be more specific? I really don't think this is the case - if I remember correctly, the ILOVEYOU virus used an attachment name like ILOVEYOU.TXT.VBS and was displayed as ILOVEYOU.TXT with a VBScript icon (a wavy scroll that looks similar to Notepad's icon but not the icon for text files). Perhaps you're thinking of the EXPLORE.ZIP virus? That was an executable with an attachment name like EXPLORE.ZIP.EXE, and executables can contain their own icons; it used WinZip's icon for Zip files.
C++ uses the same token for assignment, initialisation, specification of default arguments, specification of pure virtual functions, definition of enumerators, and probably a few other things I forgot. Is that so different?
The typical recording contract for a new artist seems to be somewhere between a loan and an investment (venture capital) from the studio, yet worse than either (from the point of view of the artist). As far as I can see, the studios currently have enough control over distribution that artists are forced to agree to these inequitable terms if they are to have a chance of achieving the level of distribution needed to make a decent income. On the other hand maybe artists just aren't attractive investments.
Also, it would be better if the NETBEUI protocol used to access these shares were not bound to the dial-up adapter (i.e. modem). Unfortunately, all protocols are bound to all devices by default.
That's NetBIOS, not NetBEUI. NetBEUI is a lower-level protocol that you could use instead of TCP/IP; since ISPs only deal with TCP/IP they won't ever send you NetBEUI packets.
The problem is, every time the floppy drive hit an error, it would reset itself by "banging" the head repeatedly against the stop, eventually knocking it out of alignment.
This ought to be illegal under computer misuse legislation. Sadly I don't think it's practical for real people to use this against corporations.
Based on their past behaviour, I should think the big media corps will persuade governments to slap a big levy on hard drives that don't implement access control, so the ones that do will be cheaper.
Where I said "gamma ~= 2.0" what I really meant was that the images should be suitable for displaying with display gamma ~= 2.0, so image gamma ~= 1/2.0 = 0.5.
Typical CRT monitors in typical viewing conditions have a display gamma of 2.2, and LCD displays are usually set to produce a similar gamma value. Macs (or rather MacOS) have fixed software gamma-correction that produces an effective display gamma of 1.8. Both of these are subject to change depending on the monitor's settings and ambient lighting. If you want the brightness as perceived by a human to be proportional to the values generated by software then the gamma value should be about 2. Either of these values is probably "close enough".
What may be the issue here is some confusion over the "standard" gamma value for JPEG files. The JPEG spec says that to minimise visual artifacts of compression JPEG should be applied to images in a colour space whose gamma value roughly matches human perception, i.e. gamma ~= 2.0. The JFIF spec (which defines the format of everyday JPEG files) says the gamma value for JFIFs shall be 1.0.
There are (at least) two senses of the term "public domain". In this article it means "visible to the public" rather than "not covered by anyone's copyright".
That's the way Mozilla works. It's packaged together, but the major components are separated out so they won't be loaded until they're needed. You could probably delete the corresponding files without breaking Mozilla, though you'd want to remove the corresponding buttons and menu items from the chrome (UI).
This is exactly the same sort of problem Windows developers have when they wish to switch from e.g. VC++ 5.0 to VC++ 6.0 but they have a third-party library (such as Oracle stuff) that was built for the older of the two.
In neither case do these problems affect end-users.
Even the standards documents are unclear on what the name of the protocol is: see the list of Internet Drafts on the IETF Secure Shell Working Group page.
They're durable. Books can be burned or soaked, but short of that they're remarkably hard to destroy. Books from centuries ago have been preserved and read, despite the aging fragility of the paper; I can't even emulate computer software that was written forty years ago.
For the last 100 years or so, most books have been printed on acidic paper that doesn't last nearly so long. Here are some 19th century Dickens novels that are already too brittle to read. Apparently alkaline paper is no more expensive than acidic paper now, though. The Alkaline Paper Advocate appears to have far more information than you could ever want about this.
You're comparing apples and oranges. QNX squeezed a demo onto a single 1.44 MB floppy. It doesn't have any provision for writable storage. It has a generic slow VGA display driver. It has just two basic applications. It's a demo. This Linux system, however, appears to be a useful foundation for product development.
Well I don't write C++ code daily. Or ever if I can help it. But the last rating I saw said that code that used the STL was almost twice as large and almost twice as slow as code that did the same thing more directly. This can easily be an unacceptable penalty.
Old benchmarks, perhaps? Some tests show that using standard library template classes (not the same thing as the STL, which is a specific implementation) instead of C idioms is a win in some places and a loss in others.
The same holds true of the Amazon one click patent, it was not until cookies came around that they could implement it
I don't see why cookies were necessary for this, any more than they were necessary to implement any kind of pseudo-session. A user ID or session ID can be associated with a request using a hidden field in a form, or by encoding it in the URL for the button.
Perhaps it will have some competition in the form of mobile phones that can run downloadable games? The first such phones have just gone on sale in Japan.
Slashdot Mirror
This legislation is already in place in the UK, leading Ross Anderson to conclude that he is an international terrorist (though not for economic reasons).
No, the icon for 'I don't know what this thing is' is a page with a Windows flag on it and one corner folded over.
Can you be more specific? I really don't think this is the case - if I remember correctly, the ILOVEYOU virus used an attachment name like ILOVEYOU.TXT.VBS and was displayed as ILOVEYOU.TXT with a VBScript icon (a wavy scroll that looks similar to Notepad's icon but not the icon for text files). Perhaps you're thinking of the EXPLORE.ZIP virus? That was an executable with an attachment name like EXPLORE.ZIP.EXE, and executables can contain their own icons; it used WinZip's icon for Zip files.
C++ uses the same token for assignment, initialisation, specification of default arguments, specification of pure virtual functions, definition of enumerators, and probably a few other things I forgot. Is that so different?
The typical recording contract for a new artist seems to be somewhere between a loan and an investment (venture capital) from the studio, yet worse than either (from the point of view of the artist). As far as I can see, the studios currently have enough control over distribution that artists are forced to agree to these inequitable terms if they are to have a chance of achieving the level of distribution needed to make a decent income. On the other hand maybe artists just aren't attractive investments.
That's NetBIOS, not NetBEUI. NetBEUI is a lower-level protocol that you could use instead of TCP/IP; since ISPs only deal with TCP/IP they won't ever send you NetBEUI packets.
This ought to be illegal under computer misuse legislation. Sadly I don't think it's practical for real people to use this against corporations.
Based on their past behaviour, I should think the big media corps will persuade governments to slap a big levy on hard drives that don't implement access control, so the ones that do will be cheaper.
Where I said "gamma ~= 2.0" what I really meant was that the images should be suitable for displaying with display gamma ~= 2.0, so image gamma ~= 1/2.0 = 0.5.
Typical CRT monitors in typical viewing conditions have a display gamma of 2.2, and LCD displays are usually set to produce a similar gamma value. Macs (or rather MacOS) have fixed software gamma-correction that produces an effective display gamma of 1.8. Both of these are subject to change depending on the monitor's settings and ambient lighting. If you want the brightness as perceived by a human to be proportional to the values generated by software then the gamma value should be about 2. Either of these values is probably "close enough".
What may be the issue here is some confusion over the "standard" gamma value for JPEG files. The JPEG spec says that to minimise visual artifacts of compression JPEG should be applied to images in a colour space whose gamma value roughly matches human perception, i.e. gamma ~= 2.0. The JFIF spec (which defines the format of everyday JPEG files) says the gamma value for JFIFs shall be 1.0.
There are (at least) two senses of the term "public domain". In this article it means "visible to the public" rather than "not covered by anyone's copyright".
That's the way Mozilla works. It's packaged together, but the major components are separated out so they won't be loaded until they're needed. You could probably delete the corresponding files without breaking Mozilla, though you'd want to remove the corresponding buttons and menu items from the chrome (UI).
This is exactly the same sort of problem Windows developers have when they wish to switch from e.g. VC++ 5.0 to VC++ 6.0 but they have a third-party library (such as Oracle stuff) that was built for the older of the two.
In neither case do these problems affect end-users.
Even the standards documents are unclear on what the name of the protocol is: see the list of Internet Drafts on the IETF Secure Shell Working Group page.
For the last 100 years or so, most books have been printed on acidic paper that doesn't last nearly so long. Here are some 19th century Dickens novels that are already too brittle to read. Apparently alkaline paper is no more expensive than acidic paper now, though. The Alkaline Paper Advocate appears to have far more information than you could ever want about this.
There's always the Alan Smithee option.
What do you mean, all 83 tracks? Plenty of floppy drives will refuse to step their heads beyond the standard 80 tracks (or rather, cylinders).
The DOI appears to be a plan for something similar to URNs, implemented by the Handle System. How does this close anything off?
This is in the interests of everyone who uses the root and top-level servers, i.e. virtually everyone using the Internet.
You're comparing apples and oranges. QNX squeezed a demo onto a single 1.44 MB floppy. It doesn't have any provision for writable storage. It has a generic slow VGA display driver. It has just two basic applications. It's a demo. This Linux system, however, appears to be a useful foundation for product development.
Old benchmarks, perhaps? Some tests show that using standard library template classes (not the same thing as the STL, which is a specific implementation) instead of C idioms is a win in some places and a loss in others.
The Boeing 777's auto-pilot is apparently capable of landing the plane completely automatically.
I don't see why cookies were necessary for this, any more than they were necessary to implement any kind of pseudo-session. A user ID or session ID can be associated with a request using a hidden field in a form, or by encoding it in the URL for the button.
The page referred to states that O'Reilly put up the bounty, not Bezos.
Perhaps it will have some competition in the form of mobile phones that can run downloadable games? The first such phones have just gone on sale in Japan.