PF "losses" are not losses, it is power that is in effect returned back to the source. One can simply treat it as power that isn't delivered at all. Therefore the original posting can be considered as essentially correct.
The obvious reason people might be getting annoyed: the side-listener is forced to participate in a social situation in which s/he is being excluded. The effect is similar to being snubbed.
The Semantic Web seems to be a generalized version of metatagging combined with a search engine tailored to the format. To work well, this requires 1) everyone to think hard and attach to their pages the appropriate semantics, and 2) that there are few people in the world that deliberately associate all sorts of junk with their web pages in order to get the page to appear in everyone's semantic search.
For starters, read this interview with
Con Kolivas. He is a doctor from Australia who as a hobby has been poking around in the Linux kernel, submitting contributions in whatever areas he becomes inspired about.
His example is a great way to remain a doctor and become a major figure in another field at the same time.
In related news, Ford has started a project to replace the aging wheel design (3,000 years out of date now) with a new python-transport. With only four of these powerful snakes, every vehicle will be able to slither around more reliabily and across all sorts of terrain forever untraversable by the obsolete and despicible wheel design.
Homer's Odyssey, I believe, mentions in passing that dropped food was defiled food. I imagine you could be executed for reusing dropped food (if a servant) or become shunned or exiled if a member of the upper class. Either seems like an appropriate punishment to me:)
PCI Express is packet based which makes operation of memory mapped devices across it exceptionally inefficient, both in bandwith and latency. So I would be suprised if PCI Express replaces AGP, where the primary interface is a huge direct-mapped on-board memory that video drivers directly paint the desired picture via massive use of load and store instructions.
Where PCI Express will really shine is in block transfer devices such as HD and CD-ROM and high volume streaming devices such as those producing video and audio streams.. all naturals for packetized transmission.
The author must have been smoking something. I just drilled down a bit into USB home and I see no reference to renaming USB 1.1 to USB 2.0. They have renamed USB 1.1 to USB Full-Speed and USB 2.0 to USB Hi-Speed and use those new names consistantly throughout their web pages. Though the renaming was hardly necessary, it is unambiguous and isn't really any different than the periodic product renaming done in most industries for 'marketing reasons'.
Information is lost in compilation. You can never reconstruct the exact original source
So what? Doing reasonable interpolations in context is what brains are for. Example: IIRC, when the Morris Worm appeared in 1989, Gene Spafford examined the binary and reverse-engineered the C code, sprinkling it with meaningful comments and good variable and function names. When the original source became available, his turned out to be cleaner program than the original. That is, he not only recreated the original in every way that counts, he overshot and did better than the original
Common code doesn't mean Linux took from SCO
on
What if SCO is Right?
·
· Score: 2, Interesting
Just because (and if) there is common code between Linux and SCO UNIX doesn't mean that the Linux camp 'borrowed' the code. It could have just as easily been the other way around. In fact, given the public nature of Linux code and the hidden nature of SCO's, that is more likely to be what happened.
nothing new here, curses(3) does it all
on
Who Needs XFree86?
·
· Score: 1
The review is of Twin, the very cool windowing environment for the console.
What's new here? Curses(3) does everything twin does, and has been around and heavily used since the 70s.
Screen(1) uses curses to support multiple virtual terminals on one physical terminal.
vi(1) uses curses for text editing. Very likely emacs(1) does so too.
Lots of text based admin programs out there, all using curses, eg, top(1), mpstat(1), watch(1).
And several of these programs use multiple windows a-la X, as curses supports that too and always has.
Didn't anybody read the pdf whitepaper? The only thing common between serial SCSI and SATA is the connector and the power and ground pins on the connector. The two protocols use entirely different signal waveforms and higher level protocols on the signaling pins. The article specifically states that to plug the wrong device into the connector results in a nonfunctional unit.
The real problem with micropayments is supplier fraud: they use teasers (ie, google hits) to make you think they have what you want, you get it and it isn't what you want. Yet they collect the micropayment for the hit.
Then there is the problem of salami-slicing: micropayments encourage vendors to break up any actually useful info into as many little bits as they can possibly get away with. You hit the first bit, find it useful (make a micropayment), go fetch the next bit, make another micropayment, and so on. With micropayments, the incentive to create comprehensive web pages, pages that present the needed info succintly and showing the proper relationships amoung the elements of the data, would disappear.
Finally, we need the ability to browse around, looking for what it needed, before payments are made; paying only the hits that actually prove useful. Micropayments fail this test big-time.
That was supposed to be CD-R, of course. I suppose I should make an effort to change my habits and start burning the Quickn data to a pair of CD-RWs....
I write my Quickn data out to a pair of floppies (duplicatied backup) at the end of each session. CD-RW would suck at that; the desired lifetime of the backup is only until I do the next backup, while CD-RW is forever.
Very interesting article. Thank you for pointing it out. Unfortunately, the article says that laches only prevents one from collecting past royalties and penalties,while leaving the ones from the time the suite was filed onwards fully collectable. The relevant text:
To the extent the defense bars suits or limits recovery of damages, its effect is similar to but less severe than that of a statute of limitations. Laches differs from a statute of limitations in that it fails to constitute a complete defense against patent holders' lawsuits. Patentees against whom the laches defense has been successfully invoked are barred from collecting only those damages that accrued prior to filing suit./5/ Patentees may recover damages flowing from infringing conduct that takes place after commencement of an infringement action, even where the accused infringer successfully invokes the laches defense
I'd say he described a need for comprehensive, well thought out binary APIs within the kernel, APIs that stay frozen or expand in a binary compatible way over time.
All that is really needed is a driver API and possibly a filesystem API for the bulk of these problems to be solved.
Slashdot Mirror
PF "losses" are not losses, it is power that is in effect returned back to the source. One can simply treat it as power that isn't delivered at all. Therefore the original posting can be considered as essentially correct.
The obvious reason people might be getting annoyed: the side-listener is forced to participate in a social situation in which s/he is being excluded. The effect is similar to being snubbed.
The Semantic Web seems to be a generalized version of metatagging combined with a search engine tailored to the format. To work well, this requires 1) everyone to think hard and attach to their pages the appropriate semantics, and 2) that there are few people in the world that deliberately associate all sorts of junk with their web pages in order to get the page to appear in everyone's semantic search.
It appeals to the vanity of the author, or (more important) to those who paid the author to write it.
His example is a great way to remain a doctor and become a major figure in another field at the same time.
We will have good software the day software companies face the same kind of liability that, say, Ford faced for the Pinto exploding gas tank.
In related news, Ford has started a project to replace the aging wheel design (3,000 years out of date now) with a new python-transport. With only four of these powerful snakes, every vehicle will be able to slither around more reliabily and across all sorts of terrain forever untraversable by the obsolete and despicible wheel design.
Have you looked at bitkeeper? It is a fantastic source-control system, and has a reasonable OSS-project free-use license.
The easiest way for Microsoft to get around this patent is to purchase from Flash, Adobe, etc rights to embed their plugins as an intrinsic in IE.
Homer's Odyssey, I believe, mentions in passing that dropped food was defiled food. I imagine you could be executed for reusing dropped food (if a servant) or become shunned or exiled if a member of the upper class. Either seems like an appropriate punishment to me:)
Linuxthreads will still be present and will work just the same for old binaries or for new binaries compiled against it.
PCI Express is packet based which makes operation of memory mapped devices across it exceptionally inefficient, both in bandwith and latency. So I would be suprised if PCI Express replaces AGP, where the primary interface is a huge direct-mapped on-board memory that video drivers directly paint the desired picture via massive use of load and store instructions.
.. all naturals for packetized transmission.
Where PCI Express will really shine is in block transfer devices such as HD and CD-ROM and high volume streaming devices such as those producing video and audio streams
The author must have been smoking something. I just drilled down a bit into USB home and I see no reference to renaming USB 1.1 to USB 2.0. They have renamed USB 1.1 to USB Full-Speed and USB 2.0 to USB Hi-Speed and use those new names consistantly throughout their web pages. Though the renaming was hardly necessary, it is unambiguous and isn't really any different than the periodic product renaming done in most industries for 'marketing reasons'.
So what? Doing reasonable interpolations in context is what brains are for. Example: IIRC, when the Morris Worm appeared in 1989, Gene Spafford examined the binary and reverse-engineered the C code, sprinkling it with meaningful comments and good variable and function names. When the original source became available, his turned out to be cleaner program than the original. That is, he not only recreated the original in every way that counts, he overshot and did better than the original
Just because (and if) there is common code between Linux and SCO UNIX doesn't mean that the Linux camp 'borrowed' the code. It could have just as easily been the other way around. In fact, given the public nature of Linux code and the hidden nature of SCO's, that is more likely to be what happened.
What's new here? Curses(3) does everything twin does, and has been around and heavily used since the 70s.
Screen(1) uses curses to support multiple virtual terminals on one physical terminal.
vi(1) uses curses for text editing. Very likely emacs(1) does so too.
Lots of text based admin programs out there, all using curses, eg, top(1), mpstat(1), watch(1).
And several of these programs use multiple windows a-la X, as curses supports that too and always has.
Who uses wheels anyway? They are SO three thousand generations ago.
Simplicity counts for something, you know.
Didn't anybody read the pdf whitepaper? The only thing common between serial SCSI and SATA is the connector and the power and ground pins on the connector. The two protocols use entirely different signal waveforms and higher level protocols on the signaling pins. The article specifically states that to plug the wrong device into the connector results in a nonfunctional unit.
The real problem with micropayments is supplier fraud: they use teasers (ie, google hits) to make you think they have what you want, you get it and it isn't what you want. Yet they collect the micropayment for the hit.
Then there is the problem of salami-slicing: micropayments encourage vendors to break up any actually useful info into as many little bits as they can possibly get away with. You hit the first bit, find it useful (make a micropayment), go fetch the next bit, make another micropayment, and so on. With micropayments, the incentive to create comprehensive web pages, pages that present the needed info succintly and showing the proper relationships amoung the elements of the data, would disappear.
Finally, we need the ability to browse around, looking for what it needed, before payments are made; paying only the hits that actually prove useful. Micropayments fail this test big-time.
We don't pay NASA to refute crackpots, we pay them to fly missions.
That was supposed to be CD-R, of course. I suppose I should make an effort to change my habits and start burning the Quickn data to a pair of CD-RWs....
I write my Quickn data out to a pair of floppies (duplicatied backup) at the end of each session. CD-RW would suck at that; the desired lifetime of the backup is only until I do the next backup, while CD-RW is forever.
That takes 5 ops. It can be done in 4: A&B | (A|B)&C
I'd say he described a need for comprehensive, well thought out binary APIs within the kernel, APIs that stay frozen or expand in a binary compatible way over time.
All that is really needed is a driver API and possibly a filesystem API for the bulk of these problems to be solved.