Germany already has a WWII era patent on a self-fueling crematorium. The trick seemed to be to have enough body fat left on the corpses to sustain the fire. So, all you need to do to have an excess of energy is to burn the fat cats.
I did remove all of my anti-virus software and move to code with many fewer vulnerabilities. Is it perfectly secure? No, but it is closer than any other OS I can use. All I can say is 'Thanks Theo'. Running OpenBSD does have costs for me, since its harder to access some multimedia and java applets and I am running slightly older packages than I would if I was running FreeBSD, or many Linux distros.
I also stopped using condoms, since I limit my activities to my wife. I'm also free from those sorts of infections because I was fortunate in my choice of a partner. This also has a cost, I'm sure that sex with other partners could be enjoyable. I also know that the 'zipperless f*ck' is more common in fiction that in my world, so I'm willing to stick with my spouse.
I know you are being tongue in cheek, but there is an error in thinking if you cure the symptom rather than the root cause.
If you can't trust your partners to be safe, why don't you consider finding safe partners? In this regard, Microsoft is like the town *****. If you can't trust your partners, or if you are unwilling to live with some restrictions, by all means install antivirus software and use a condom.
They can be 'nailed' because this is a public site run by a government agency (other than Congress). This means that they are expected to code to Section 508 of the Americans with Disabilities Act. If some of the other posters are correct that this is an internal application that was then made public, this oversight is certainly understandable. It does seem to me that is was predictable that using a web site to share information about victims of a disaster would be something that FEMA might want to make public. For this reason, I see this episode as one simple example of FEMA being caught unprepared by events that I would have expected them to have 'gamed' and have developed contingency plans to address. If they had forseen such a case, I would have expected that they would have been careful to be sure and make the site accessible. Since Section 508 practically defines web accessiblity for US agencies, I would have expected Section 508 conformance. Using IE is certainly a non-issue relative to any of the horrors faced by the victims. This is no cause toto hyperventalate, but is should be a 'lessons learned' for next time.
Lessig is a law professor at Stanford. He has been before the Supreme Court arguing a case involving copyright law. So, he is actually a rather gifted lawyer. You can confirm this by Googling for 'Lessig' and go to the first hit. Click on Bio, and you are at http://www.lessig.org/bio/short/
Keep your quarter, you are the one who needs to buy a clue.
There are serious (peer reviewed) articles from NOAA (see http://www.gfdl.noaa.gov/reference/bibliography/20 04/tk0401.pdf and references in it, for example ) that certainly make for a plausible correlation between rising CO2 levels and increasingly severe hurricanes. It is quite a stretch to blame this on GW personally. But his administration is doing practically everything in its power to deny global warming and to delay any action that may be harmful to economics interests. I think he is placing himself squarely on the wrong side of history. Future generations will marvel at our denial of sustainability as a foundation for stable economic systems.
Herbert Hoover wasn't personally responsible for the Great Depression, but he is forever associated with the Crash of '29. In a similar way, Lois XIV is associated with the excess of the French Aristocracy. I hope that Bush isn't associated with the end of the American Century, but I have a sinking feeling that the US is courting disaster. It will not be GW's fault, but he isn't going to be part of the solution either.
I have read some of the earlier TCO studies by the Robert Francis Group. They are not marketing drivel. TCO studies are difficult to compare and you do need to read the fine print. But is isn't that hard to see how RFG & MS make different assumptions and these lead to different results. I fould that the RFG reports made better supported assumptions. For example, they observed that a single admin can manage significantly more Linux (or Solaris) boxes that a typical Windows Admin. So, they took this and the salary differences into account to determine the cost of administration. (This is more significant than the cost of OS licensing, by the way). The MS-funded studies took into account the higher cost of *nix admins, but assumed that all admins can administer the same number of machines. Of the two assumptions, I believe that the RFG assumptions are the more realistic. Some people are bullshitters, but that doesn't mean that everyone in the same business is also a bullshitter. Read and make up you own mind as to who belongs in each that catagory.
I agree completely. Here is one example. A dissertation is often printed about three times (one for the department, one for the univerisity library and once for the student to keep). If the document is shared, it is shared electronically. What are the odds that you can read an Word 3.0 document compared with the odds that you can read a PDF, LaTeX or even RDF? It blows me away that people will work hard to produce a document that should become part of the corpus of human works, and then save in in a format that will be dead in a few years.
If it took you seven seconds, you clearly didn't read the EULA. So how would you inow if it 'fancy' (or pick any other adjective, you still wouldn't know because you didn't read it.) I am sufficiently paranoid about licenses that I prefer BSD-style licenses to the GPL and the GPL to most commercial licenses.
I saw that too. I think he tried to add a 'credible reference', but didn't bother to see if the link referenced the right 'ATA'. Hope he's hungry enough for the egg on his face.
12. A system for emphasizing numerical data contained in an electronic document containing both text data and numerical data, the system comprising: a word processing application program operative to permit the editing of the text data and the numerical data within the electronic document; and a dynamically linked library configured for use with the word processing application program, the dynamically linked library operative to receive a request to emphasize all of the numerical data in the electronic document and to locate all of the numerical data contained within the electronic document and emphasize only the located numerical data in response to receiving the request.
In order to violate the patent, you have to violate both claim 1 and claim 12. Claim 2-11 are 'embelishments' on claim 1 and the claims following 12 are embelishments on cliam 12. There have been several examples given of perl scripts and so forth that violate claim 1 and certainly are proir art. But I haven't seen examples that violate both claims. Even if gnumeric were to 'steal' this technique of highlighting numbers,it would be hard for Microsoft to sue since they would have a hard time convincing a judge that a 'word processor' was involved.
But, I would think that a macro called from within an HTML editor that surrounded every 'number' with
<em> would be a potential violation, especially if the macros were processed by a dynamically linked library. There could be a bajillion ways that this could make life miserable for anyone who processes text. I suggest that we all start inventing new numbers not covered by the patent and staticly compiling any software for text processing.
That is probably true, I was only thinking about magazine sized photos. So, where do I find lifesize posters of Playmates? This could be a new way for Playboy to make some money....
Your example is completely off topic. Do you think that a DA is going to go into court with a paper cup that he claims is from the defendant, but he doesn't have a clearer chain of custody that 'we snitched from the trash after he left'? In the rape cases, the DNA was from samples taken legally by police of people that where properly arrested. The chain of custody for the genetic material follows careful procedures and the results can be duplicated. The privacy concerns of the arrested people have been carefully considered and they have still been required to give up their DNA in an orderly way.
What does that have to do with some employer secretly obtaining a sample that they claim is from an employee?
No it isn't. You are so stuck in procedural prgramming you miss the point. In order for your directions to work, you need to make different instructions for every location on Earth in order to assure that anyone can find your house. That isn't what you do with people. If you are dealing with somebody with a map, you give them an address and you may also give them some hints (East 14th has a lot of construction, so take Oak Stree instead). People can deal intuitively with first order logic (stuff with 'there exists an X such that...' or 'for all X, X is an element of Y', but almost none of our programs can deal with this analytically.
They could easily produce grain free centerfolds with a modern digital camera. With a high megapixel Canon digital (and probably a Nikon, and certainly a medium format with digital back) and a prime lens (e.g. the 80 mm f/1.4 in the case of a Canon or Nikon), you can count eyelashes on a full length portrait. That is plenty for an 18 inch print. What they can't do as easily is use all of the swings and tilts of a view camera to get exactly what they want in focus. (Eyes are always sharp in Playboy. You may be able to guess what else is included in the plane of sharpest focus.) In the hands of an expert, a view cameras can do amazing things that a rigid body camera cannot do.
Do you know who the author is? He is not a pie-in-the-sky dreamer. He has produced some revolutionary products (the whole concept of Bayesian spam filtering is his). He can, and does deliver. I can agree that he deals with a small fraction of the developer community, but this is because he is an elite and he only needs to deal with the elite
I don't think that the issues with IE relate to the fact that the programmers are second rate. I believe that the issues are that they are not supposed to fix things that would lead to better interoperability. It is very much to Microsoft's advantage to have all of the.Net coded intranets render well only on IE. Everytime I write an intranet app, I am not given time to worry about cross-browser support. I'm sure that this is just fine with Microsoft. If.Net web forms generated valid XHTML with full CSS support, they would render well on any browser. The incestuous relationship between ASP.Net and IE is no coincidence.
That must be because Star Trek, like Apollo and Soyuz, was a child of the sixties. I think that this design looks more like a Soyuz ( see http://en.wikipedia.org/wiki/Soviet_space_program ) with a humongus Apollo command module than anything else. It's even going to parachute to land rather than water. This is a 60's soviet design with new materials and electronics and a different flag on the side.
Drop a coffee mug from three feet. What happens to ceramics when they recieve a sharp blow, even one with little force. Now things about 'little things' in supersonic winds. A thin layer of cloth isn't going to matter all that much. It may help, but is is worth the weight?
The whole engineering exercise is terribly weight constrained. You can imagine all sorts of solutions, but they add weight. My current favorite is to sandwich foam insulation between aluminum skins. This would prevent the insulation from shedding. There are plenty of examples of this structure in nature. Our skulls for example, a skull is build of two dense layers of bone with a layer of porous bone between it. The result is stronger, stiffer and lighter than a skull made of only solid bone. But for all I know, the cold LOX would cause the inner aluminum to contract and cause the layers to pull appart. But all these what-ifs don't really matter until you plug in the numbers and figure out the weight of the entire design is and build a series of computer simulations and prototypes.
`When I use a word,' Humpty Dumpty said in rather a scornful tone, `it means just what I choose it to mean -- neither more nor less.'
Feel free to invent defintions, but don't expect the rest of us to have invented the same distictions. I'm confident that to many, ethics and morality are synonyms.
I don't believe that. After a BSOD, my hard drive really chatters for a couple of minutes as multimeg of 'essential' components like IE are installed. BSD is easly small enough to fit on flash memory, so it only chatters when I'm reading the SAMBA partitions mounted on the HD.
Perhaps the software can help lower the cost of malpractice claims. The article states that the VA greatly reduced the number of drug errors by using barcodes and software. This alone should go a long way to reducing these legitimate malpractice claims. If you add malpractice insurance into the equation, the software might pay for itself in lower premiums.
Slashdot Mirror
Germany already has a WWII era patent on a self-fueling crematorium. The trick seemed to be to have enough body fat left on the corpses to sustain the fire. So, all you need to do to have an excess of energy is to burn the fat cats.
I also stopped using condoms, since I limit my activities to my wife. I'm also free from those sorts of infections because I was fortunate in my choice of a partner. This also has a cost, I'm sure that sex with other partners could be enjoyable. I also know that the 'zipperless f*ck' is more common in fiction that in my world, so I'm willing to stick with my spouse.
I know you are being tongue in cheek, but there is an error in thinking if you cure the symptom rather than the root cause. If you can't trust your partners to be safe, why don't you consider finding safe partners? In this regard, Microsoft is like the town *****. If you can't trust your partners, or if you are unwilling to live with some restrictions, by all means install antivirus software and use a condom.
They can be 'nailed' because this is a public site run by a government agency (other than Congress). This means that they are expected to code to Section 508 of the Americans with Disabilities Act. If some of the other posters are correct that this is an internal application that was then made public, this oversight is certainly understandable. It does seem to me that is was predictable that using a web site to share information about victims of a disaster would be something that FEMA might want to make public. For this reason, I see this episode as one simple example of FEMA being caught unprepared by events that I would have expected them to have 'gamed' and have developed contingency plans to address. If they had forseen such a case, I would have expected that they would have been careful to be sure and make the site accessible. Since Section 508 practically defines web accessiblity for US agencies, I would have expected Section 508 conformance. Using IE is certainly a non-issue relative to any of the horrors faced by the victims. This is no cause toto hyperventalate, but is should be a 'lessons learned' for next time.
I love Office XXIV, but what is the motto:
'apres nous, le deluge'
or
Long live the anti-Sun/OO King
This table was from an article in 1997. How are they able to include numbers from the decade of the 90's?
reference please ....
BTW its not 'her kid ...' its 'here kid ...
Herbert Hoover wasn't personally responsible for the Great Depression, but he is forever associated with the Crash of '29. In a similar way, Lois XIV is associated with the excess of the French Aristocracy. I hope that Bush isn't associated with the end of the American Century, but I have a sinking feeling that the US is courting disaster. It will not be GW's fault, but he isn't going to be part of the solution either.
I have read some of the earlier TCO studies by the Robert Francis Group. They are not marketing drivel. TCO studies are difficult to compare and you do need to read the fine print. But is isn't that hard to see how RFG & MS make different assumptions and these lead to different results. I fould that the RFG reports made better supported assumptions. For example, they observed that a single admin can manage significantly more Linux (or Solaris) boxes that a typical Windows Admin. So, they took this and the salary differences into account to determine the cost of administration. (This is more significant than the cost of OS licensing, by the way). The MS-funded studies took into account the higher cost of *nix admins, but assumed that all admins can administer the same number of machines. Of the two assumptions, I believe that the RFG assumptions are the more realistic. Some people are bullshitters, but that doesn't mean that everyone in the same business is also a bullshitter. Read and make up you own mind as to who belongs in each that catagory.
Open formats are the clear answer.
If it took you seven seconds, you clearly didn't read the EULA. So how would you inow if it 'fancy' (or pick any other adjective, you still wouldn't know because you didn't read it.) I am sufficiently paranoid about licenses that I prefer BSD-style licenses to the GPL and the GPL to most commercial licenses.
I saw that too. I think he tried to add a 'credible reference', but didn't bother to see if the link referenced the right 'ATA'. Hope he's hungry enough for the egg on his face.
That's just silly, everyone knows Perl is for cookies.
But, I would think that a macro called from within an HTML editor that surrounded every 'number' with <em> would be a potential violation, especially if the macros were processed by a dynamically linked library. There could be a bajillion ways that this could make life miserable for anyone who processes text. I suggest that we all start inventing new numbers not covered by the patent and staticly compiling any software for text processing.
That is probably true, I was only thinking about magazine sized photos. So, where do I find lifesize posters of Playmates? This could be a new way for Playboy to make some money....
What does that have to do with some employer secretly obtaining a sample that they claim is from an employee?
No it isn't. You are so stuck in procedural prgramming you miss the point. In order for your directions to work, you need to make different instructions for every location on Earth in order to assure that anyone can find your house. That isn't what you do with people. If you are dealing with somebody with a map, you give them an address and you may also give them some hints (East 14th has a lot of construction, so take Oak Stree instead). People can deal intuitively with first order logic (stuff with 'there exists an X such that ...' or 'for all X, X is an element of Y', but almost none of our programs can deal with this analytically.
They could easily produce grain free centerfolds with a modern digital camera. With a high megapixel Canon digital (and probably a Nikon, and certainly a medium format with digital back) and a prime lens (e.g. the 80 mm f/1.4 in the case of a Canon or Nikon), you can count eyelashes on a full length portrait. That is plenty for an 18 inch print. What they can't do as easily is use all of the swings and tilts of a view camera to get exactly what they want in focus. (Eyes are always sharp in Playboy. You may be able to guess what else is included in the plane of sharpest focus.) In the hands of an expert, a view cameras can do amazing things that a rigid body camera cannot do.
I don't think that the issues with IE relate to the fact that the programmers are second rate. I believe that the issues are that they are not supposed to fix things that would lead to better interoperability. It is very much to Microsoft's advantage to have all of the .Net coded intranets render well only on IE. Everytime I write an intranet app, I am not given time to worry about cross-browser support. I'm sure that this is just fine with Microsoft. If .Net web forms generated valid XHTML with full CSS support, they would render well on any browser. The incestuous relationship between ASP.Net and IE is no coincidence.
That must be because Star Trek, like Apollo and Soyuz, was a child of the sixties. I think that this design looks more like a Soyuz ( see http://en.wikipedia.org/wiki/Soviet_space_program ) with a humongus Apollo command module than anything else. It's even going to parachute to land rather than water. This is a 60's soviet design with new materials and electronics and a different flag on the side.
The whole engineering exercise is terribly weight constrained. You can imagine all sorts of solutions, but they add weight. My current favorite is to sandwich foam insulation between aluminum skins. This would prevent the insulation from shedding. There are plenty of examples of this structure in nature. Our skulls for example, a skull is build of two dense layers of bone with a layer of porous bone between it. The result is stronger, stiffer and lighter than a skull made of only solid bone. But for all I know, the cold LOX would cause the inner aluminum to contract and cause the layers to pull appart. But all these what-ifs don't really matter until you plug in the numbers and figure out the weight of the entire design is and build a series of computer simulations and prototypes.
Feel free to invent defintions, but don't expect the rest of us to have invented the same distictions. I'm confident that to many, ethics and morality are synonyms.
And the HURD will be running on GaAs processors so we can finally up the clock rate into the GHz range and use optical fiber rather than copper.
I don't believe that. After a BSOD, my hard drive really chatters for a couple of minutes as multimeg of 'essential' components like IE are installed. BSD is easly small enough to fit on flash memory, so it only chatters when I'm reading the SAMBA partitions mounted on the HD.
Perhaps the software can help lower the cost of malpractice claims. The article states that the VA greatly reduced the number of drug errors by using barcodes and software. This alone should go a long way to reducing these legitimate malpractice claims. If you add malpractice insurance into the equation, the software might pay for itself in lower premiums.