sysadmin.ie

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

alphadogg writes "Incidents of cellphone theft have been rising for several years and are fast becoming an epidemic. IDG News Service collected data on serious crimes in San Francisco from November to April and recorded 579 thefts of cellphones or tablets, accounting for 41 percent of all serious crime. In just over half the incidents, victims were punched, kicked or otherwise physically intimidated for their phones, and in a quarter of robberies, users were threatened with guns or knives. This isn't just happening in tech-loving San Francisco, either. The picture is similar across the United States. A big reason for such thefts, until recently, is that there had been little to stop someone using a stolen cellphone. Reacting to pressure from law enforcement and regulators, the U.S.'s largest cellphone carriers agreed early last year to establish a database of stolen cellphones."

Read more of this story at Slashdot.

Underholdning writes "DRM is coming to HTML5. The W3C published a working draft yesterday of the framework that will support the use of DRM-protected media. Ars Technica's Peter Bright reports on it with an article claiming that DRM in HTML5 is a victory for the open web, not a defeat. Bright argues that if HTML5 does not support DRM, then content providers will move their content away from open standards and implement it with native apps — abandoning the web in the process. Quoting: 'Keeping it out of W3C might have been a moral victory, but its practical implications would sit between slim and none. It doesn't matter if browsers implement "W3C EME" or "non-W3C EME" if the technology and its capabilities are identical. ... Deprived of the ability to use browser plugins, protected content distributors are not, in general, switching to unprotected media. Instead, they're switching away from the Web entirely. Want to send DRM-protected video to an iPhone? "There's an app for that." Native applications on iOS, Android, Windows Phone, and Windows 8 can all implement DRM, with some platforms, such as Android and Windows 8, even offering various APIs and features to assist this.'"

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.

ais523 writes "The Federal Circuit has divided CLS Bank vs. Alice Corp., a case about various sorts of patents, including software patents. Although the judges disagreed, to a lesser or greater extent, on the individual parts of the ruling, more than half decided that the patents in question — algorithms for hedging risk — were ineligible patent matter, and that merely adding an 'on a computer'-like clause to an abstract algorithm does not make it patentable. Further coverage is available at Groklaw, or you can read the opinion itself (PDF)."

Read more of this story at Slashdot.