Have none of the above posters read the article or draft license? All the GPL3 requires is that if some code already includes a "send me the code" feature, any modifications may not remove it. It doesn't mean every GPL3'd application must publish its code in this way.
There's a fantastic archive at gopher.quux.org . I don't think there's anything there which isn't accessible on the Web, but it's nice to see something useful on Gopher.
The best thing about this site is that it's still accessible when our shonky Web cache breaks. If you're incapable of doing any work without the Web, at least you can read Project Gutenberg, the Jargon File, or the Internet Oracle archives from here.
(BTW: there are a few broken selectors on this site at the moment; unfortunately some of the most useful stuff. Hopefully it'll be fixed soon.)
This is a common misconception. You're confusing the clipboard with the primary selection. Cut and paste works just like Windows', and is in fact more powerful.
X's clipboard is generally handled with interprocess communication, not buffers. If you select something, the application claims the primary selection. Middle-clicking somewhere else will ask the application to send the selection.
Copy and Paste use the clipboard, which is entirely separate. Edit/Copy in Mozilla claims the clipboard, setting its value to the current selection. As you have to select the text first, this must overwrite the primary selection, but selecting something else will change the selection without affecting the clipboard. Try selecting something in Mozilla, ^C, then select something else. Middle-click and ^V will enter different things. If you ignore the primary selection, this is exactly the same as Windows, but the ability to select and paste short items quickly using only the selection can be very useful - especially as it doesn't affect the clipboard.
Unfortunately it's impossible to use the clipboard in xterm; you have to use the selection. You can cut and paste between most other applications, though. Another problem was in an old implementation of (IIRC) Qt, which overwrote the clipboard whenever the primary selection changed. This is fixed in the latest version.
It's not problems with the security APIs that cause exploits. It's the bugs in other APIs, like XP's recent plug and play exploit.
Even despite the fact that security through obscurity is no security, how does closing the security API make the system more secure? Surely all this achieves is to allow Microsoft to put backdoors in Windows' security features.
I recently purchased a Meccano set which included the blueprints for the Analytical Engine version 4, which I built and it works fine but it would be nice to have a printer to go with it. Do I need to upgrade to Lubricating Oil Pack 3 to be able to use it?
Unfortunately commercialism is unavoidable in many aspects of science, such as medical research.
The reason is that such vast projects need to be paid for, and governments will not spend millions of zorkmids of public money on a project which will then be given away free to the entire world. Research in medicine always ends up being funded by private investiture, which will only happen if there's some profit to be made out of it.
Unfortunately, if governments force research information to be made public, it will stop being economic to do research as there would be no potential for profit. So projects like this would no longer be undertaken, simply because there'd be no financial incentive.
The release of the human genome under Open Source is an important step forward, but governments cannot and will not do this on a regular basis. If they did, no research would ever take place.
But will they GPL it? I hope whatever licence they use will exclude paying for permission to duplicate.
Slashdot Mirror
Have none of the above posters read the article or draft license? All the GPL3 requires is that if some code already includes a "send me the code" feature, any modifications may not remove it. It doesn't mean every GPL3'd application must publish its code in this way.
There's a fantastic archive at gopher.quux.org . I don't think there's anything there which isn't accessible on the Web, but it's nice to see something useful on Gopher.
The best thing about this site is that it's still accessible when our shonky Web cache breaks. If you're incapable of doing any work without the Web, at least you can read Project Gutenberg, the Jargon File, or the Internet Oracle archives from here.
(BTW: there are a few broken selectors on this site at the moment; unfortunately some of the most useful stuff. Hopefully it'll be fixed soon.)
This is a common misconception. You're confusing the clipboard with the primary selection. Cut and paste works just like Windows', and is in fact more powerful.
X's clipboard is generally handled with interprocess communication, not buffers. If you select something, the application claims the primary selection. Middle-clicking somewhere else will ask the application to send the selection.
Copy and Paste use the clipboard, which is entirely separate. Edit/Copy in Mozilla claims the clipboard, setting its value to the current selection. As you have to select the text first, this must overwrite the primary selection, but selecting something else will change the selection without affecting the clipboard. Try selecting something in Mozilla, ^C, then select something else. Middle-click and ^V will enter different things. If you ignore the primary selection, this is exactly the same as Windows, but the ability to select and paste short items quickly using only the selection can be very useful - especially as it doesn't affect the clipboard.
Unfortunately it's impossible to use the clipboard in xterm; you have to use the selection. You can cut and paste between most other applications, though. Another problem was in an old implementation of (IIRC) Qt, which overwrote the clipboard whenever the primary selection changed. This is fixed in the latest version.
It's not problems with the security APIs that cause exploits. It's the bugs in other APIs, like XP's recent plug and play exploit.
Even despite the fact that security through obscurity is no security, how does closing the security API make the system more secure? Surely all this achieves is to allow Microsoft to put backdoors in Windows' security features.
I recently purchased a Meccano set which included the blueprints for the Analytical Engine version 4, which I built and it works fine but it would be nice to have a printer to go with it. Do I need to upgrade to Lubricating Oil Pack 3 to be able to use it?
Unfortunately commercialism is unavoidable in many aspects of science, such as medical research.
The reason is that such vast projects need to be paid for, and governments will not spend millions of zorkmids of public money on a project which will then be given away free to the entire world. Research in medicine always ends up being funded by private investiture, which will only happen if there's some profit to be made out of it.
Unfortunately, if governments force research information to be made public, it will stop being economic to do research as there would be no potential for profit. So projects like this would no longer be undertaken, simply because there'd be no financial incentive.
The release of the human genome under Open Source is an important step forward, but governments cannot and will not do this on a regular basis. If they did, no research would ever take place.
But will they GPL it? I hope whatever licence they use will exclude paying for permission to duplicate.