All I really know is that even Nintendo discourages the practice. Perhaps its because of the difficulty in estimating remaining charge -- who knows? What I do know is that rechargables START at 1.5V and only drop from there, even if it's a much more gradual decline. Meanwhile, the electronics still requires 3V and you're supplying 2.4. I don't have datasheets, but I'd imagine that you can't drop very much lower before the whole thing simply fails.
In my entire history at GMail, though, I've gotten one mis-marked legitimate message; and if someone else had been reading my incoming messages he would have thought it was spam too. I think this statement bears repitition, as possibly the best way to benchmark spam filter performance realistically.
More like, do you have a multicore? Wine is good, but not very efficient. Which might be okay, except he's claiming several background disk intensive processes. A faster disk would likely also help. So now you've got a potentially CPU loaded system trying to juggle disk access in the background. DMA helps, but perhaps it's leading to excessive amounts of locking? As in "well, wine could continue, but it needs access to kernel structure slab which is currently locked until DMA completes".
An easy way to diagnose this is to put up a system monitor that displays, system, user, iowait and idle times. GNOME's system monitor applet does this but has a horrible default iowait color indistinguishable from black. Make it yellow, since it's drastically different than sys or user times;)
They're also bunk on the voltage: they register 1.2V, as is often the case with rechargables. I picked some up for Wiimote controls, and their usable lifetime is crap. Either the voltage drops below threshold quickly, or the voltage regulator is causing large inefficiencies. For batteries marketed as useful for electronics, I find the shortcoming less than applaudable.
You're thinking about this the wrong way -- on the surface it appears that mturk is an internet labor site, but as you notice, the prices are too low. Mturk provides a framework that both humans and computers can use to solve the same financially interesting problems. Essentially, it provides both incentive to solve problems by hand (though very modest), and a much larger incentive for AI researchers to attack the problem head on, and solve the entire problem set nearly at once. Of course, it does require that the party with the financially motivated problem be willing to disclose it to the world. And there needs to be more publicized case studies of mturk's effectiveness, or even the people who do have such problems won't stop to consider it.
I can't tell whether the current price structure suggests that this has already happened, or that the supply of human intelligence is so vast that it doesn't matter. I do know that several people have written tools to help them solve HITs faster, by grabbing new HITs in the background, and optimizing the display for their needs. But I wonder how much cheaper you could make HITs if you wrote the instructions in Chinese.
They're not, at least not like you're thinking (802.11 security). They're regulating consumer devices and the regulated radio spectrum, and requiring some form of lockout from being able to use consumer equipment to monitor, broadcast or interfere with regulated spectrum. To this end, they've been making decisions on security. The implication here is that the FCC expects some lockdown measures to be done entirely in software. It also suggests that some vendor has already done this. I wonder how much crytographical experience the FCC has in its employees, and how that knowledge was consulted in the decision.
Unfortunately, it also gives creedence to the people suggesting that the FCC regulations require closed source layers.
It's probably too late for my comment to be highly moderated, but really, if you want to be involved in a large and existing project, you have two choices. The first one is to fix bugs. The second way is to write documentation. Some people suggest TODO lists, but those are usually the hard parts that developers intentionally put off until there's nothing else they can feasibly do. What you really want is experience going through the motions of finding code, reading it, evaluating it, suggesting an improvement and following through.
If you're a linux user for some time, I hope you've become accustomed to the practice of filing bugs with your distribution. Pick one that annoys you and decide to fix it. This is a very common way for a user to become a developer: fixing the problems that are important to them. That you haven't done this yet suggests you don't have such a pet bug. Trying to fix someone else's bug is usually painful. First you have to be able to duplicate the problem, then make sure it's a problem with the code, that it's not fixed in CVS, etc.
This is why I suggest that you write or verify documentation, especially man pages. There's numerous advantages to this approach: * man pages have a standard format that you can learn and follow to guide you * man pages are a standard tool everyone else uses to find information * it demonstrates your ability to communicate eloquently in written language * it requires you to read source code and become familiar with a lot of the body of the code * your contribution will not be limited by your ability to understand obscure coding mistakes or hardware interactions you can't reproduce * there are far fewer people writing documentation than fixing bugs * using the revision history to determine when a feature was added is far simpler than determining when a bug was introduced * if there's a crazy build system, you won't be required to figure it out, though it would make sense to so you can write about it;)
Because you've taking a holistic approach to contributing, you'll be one of the few contributers who knows the whole source code. And you'll know so much of functionality that determining which reported bugs are configuration errors versus genuine bugs in code will be easier.
Well, I'm referring more to "Open Source Politics", "Open Source Journalism," or "Open Source Photography" where it's not about software, but very much wants to ride on the Open Source Software boat. It just presses a silly personal button to see the liberal use of the phrase Open Source to denote a certain concept of sharing. Open source isn't just about being able to modify and distribute changes, it's about having access at the same level as the authors to the preferred medium of change, hence the term Source.
It's been a lot better now, that Creative Commons has stepped up to codify a range of intellectual properties not explicitly software. So probably rather than beating someone over the head for Open Source Government, an encouraging letter from the CC would be in order;)
The open source hobbyist nature of mythTV attracts the kind of people who'd rather spec out their own hardware and help tweak the software. But the reason you can't find any for sale is probably because you didn't think to look at the ads.
That would be because Dell is large enough (and smart enough) to eliminate middlemen. They don't build their own laptops, but they do contract to have laptops built explicitly for them, similar to how the OLPC was done. system76 on the other hand, seems to rebrand Acer laptops. I wonder how they'll cope with Dell's entrance. Not well, I imagine.
it destroys the concept of a meritocracy, How much merit is there in having more free time than another person? Is playing a game, intended as entertainment, as though it were a full time job what we call "working hard" in America anymore?
What the hell are you smoking? He's not talking about shopping for diseases. He's talking about shopping price. What I'm on about is that because of deductibles, I have a market incentive to NOT file claims. That's the sort of thing you expect to happen when you remove all market incentives. The best ACL surgeon is the one least likely to kill you, and most likely to heal you. That's one hell of a tradeoff to make for dollars. HMOs handle the hard work here of excluding "bad" or "expensive" doctors. It's entirely possible that someone else's HMO refuses to cover your visit should you pick one of the two best ACL surgeons in the state.
Market incentives are great, but most people simply don't have access to the data that counts. Sicko covers the incentives program in socialized health care: they do exist, but for different people. Doctors are given incentives to get people to stop smoking, and for the highest percentage of patients arriving for wellness checkups. And the vast majority of the film is dedicated to how HMOs respond to those market pressures: they make more money denying health care than providing it.
We invent new technology, expect to use it, and expect that costs won't rise. Huh? We're expecting to get more for less. That only works for computer hardware. (in a socialist medicine system, quotas and delaying tactics are used to fight this problem)
When costs rise, we don't expect higher than average margins. All the HMOs have experienced major returns recently, and Moore's film mentions this. He doesn't speculate on why, however. Which I think is a bit unfortunate.
The attitude is "I'll pay anything to save my dying children!". We then act all offended that the hospital bill heads toward infinity. Since death is common (100% of your children will die!) you can expect to pay until you can pay no more or until we run out of technology to sell you. (as above, socialist systems deny you this choice)
How much is another six months worth to you personally? How much additional loans would you take out to extend your life by six months (or ten years)? In a free market scenario, you take out as many loans as you can to support yourself and your family to survive. The children of the poor will suffer poor care while the children of the rich will live life to the fullest money can buy. This is a (if not the) fundamental problem with free market health care. Life extending health care's value approaches infinity. All I can say is, your phrasing makes you a bastard, and by your own logic you should kill yourself now to spare the potential expenses you'll incur in living life.
Simple economics is causing all service industries to be relatively more expensive. The factory worker is now more productive because he has huge machines. The high-tech worker is absurdly productive because he only produces digital data which is trivial to replicate. The hospital worker, like the college professor, is not getting such huge productivity increases. Widgets and software can be sold cheaply while still paying the workers well, but hospital services can not be made cheap while paying the workers well. Because everything is relative, hospital costs skyrocket.
So despite the heavy economic incentive currently available, no huge increase in productivity is being found. There's likely a large number of reasons for this, like the definition of productivity, the unintended drug-prohibition side effect of junkies faking illnesses in ERs to get a fix, and a lopsided bargaining table with HMOs. But even if that's all bunk or acceptable, there's still a failure of the market to find inefficiencies.
Over in India, patients have a very limited ability to sue for malpractice and pain and suffering and... Medicine is cheap there....Before a jury, it looks good to have done more intervention.
How on earth does malpractice insurance correlate with the price of medicine? They're two fundamentally different aspects of health care and it's becoming clear you don't understand it. Drug companies in the US defend their pricing strategy as recovering costs. By "costs" they mean "paying universities for their findings, free samples for doctors, and buying large ads telling you to ask your doctor about a specific drug".
Cesearian is in no way a cover your ass maneuver. It correlates with an increased mortality rate, quite sharply. It seems most critics feel this is because the hospital can charge more for a C-section than a normal birth. Recall that at the same time our insurance agencies are booming hospitals are becoming broke. I'd wager a good number is also due to vanity.
Our health insurance is too good at insulating us from the costs of various procedures. We don't shop around for a good deal.
Bullshit. My last insurance had a premium and high deductibles. I'm not about to go shopping for diseases I don't have. Others might (re: drug addictions), but good luck. And if the expensive lot downtown is truly expensive, your HMO probably doesn't have it on its "preferred" list -- their primary legitimate objective is to reduce
For an undergraduate course, your complaints are sound. But at the graduate level, we're faced with a serious problem: the state of the art is so incredibly vast that preparing you to build on the body of existing work takes some time. At some point a grad student needs to be exposed to the papers and difficult problems that people face. Unfortunately, most math classes focus on the same problem set oriented homework instruction, even at the graduate level. It's an important experience to try to solve difficult problems, but as you noted, you had to go outside of class material to discover the solution. Whats worse is that the instructor probably forbade you from looking at such materials, as cheating. What should happen is a standard format of "here's a hard problem, try to prove it". And then present the paper as part of the course. We essentially teach students to ignore the journals they will eventually publish in.
If I might direct your ignorant ass to Amendment 14, it clearly states "All persons born or naturalized in the United States, and subject to the jurisdiction thereof, are citizens of the United States and of the state wherein they reside." Thanks for playing.
As a citizen of Kansas, I would welcome moderate federal regulation of content over the wacknuts who would be inevitably selected to regulate such affairs.
Here's the question - is non-gene DNA/machinery/ or/DATA/? Non-gene DNA is data -- ribosomes and RNA polymerase are the machinery. I like to think of them as compilers. Chemistry is the real computer, ribosomes etc are among the most important programs. Interestingly, they're sophisticated enough to "compile" themselves, I think. There's some level of control in the data itself as to what gets transcribed: promoter and inhibitor sequences, introns and exons all control what gets transcribed, and there's undoubtedly more and higher levels of expression regulation going on. I like to think of multiple ORFs as a sort of anti-cracking guarantee that removing things will have severe consequences.
Isn't there a saying that if you have physical access to the device you're already hosed? I guess they can hold themselves to higher standards, but if your laptop has been lost, it's not like I can't rip the chip out or soldier wires to it.
he people who drive most Linux development *are not* interested in desktop usability and *user* experience. This is not a troll / flamebait / cut... Maybe not, but it is an opinion backed by mere assertion. Which is equally worthless.
it's simply the truth Then I guess I'll inform Quinn Storm (Colin Quinn I think is their real name) and Compiz / Beryl that they are no longer "Linux developers." Or maybe it's not the truth. Since GNOME, KDE, OpenBox, E17 all seem to care. They have different opinions, true enough. But to say they're not interested in desktop usability is so far from the mark you deserve some +Funny moderation.
Fuck, have you looked at the firehose? It's no wonder he gets stories posted. He knows grammar and spelling and doesn't get his news from slashdot. Which is better I can say than most submissions.
Nevermind that Dell had a huge surprise earnings announcement. I've seen numerous investors and analyst question Dell's decision to lay off employees, citing their already lean head count to competitors like HP. One analyst suggested that they had gone on a hiring spree lately and perhaps they went overboard. I think your "investors love layoffs" theory is BS. It shows dedication to bring the company back from stagnation, but it's almost impossible to do right and all to often done too late to matter. In this case, I suspect the majority of people cut will be phone sales and service-- Dell seems to be moving into retail outlets, so you HAVE to assume there will be some drop off in direct sales. Five percent in sales, and the rest spread about the business isn't so bad.
But it remains to be seen where and if these cuts happen.
Re:One nice thing about Fedora7 is the buildtools
on
Fedora 7 Released
·
· Score: 2, Informative
Debian and Ubuntu use buildd. It's not as pretty as the 5 seconds I spent looking at Fedora's tool, but it gets the job done. Ubuntu uses a tool written and run by Canonical, the largest and most integrated sponsor of Ubuntu. It's also closed source, with strange promises that it will be open eventually. That said, launchpad does a hell of a lot more than monitor buildd servers. It's also a far better distro bugtracker than bugzilla is, a project planning tool etc.
Slashdot Mirror
They did, until they accepted the primary developer's conditions for accepting contributions: that the copyright be transferred to him.
All I really know is that even Nintendo discourages the practice. Perhaps its because of the difficulty in estimating remaining charge -- who knows? What I do know is that rechargables START at 1.5V and only drop from there, even if it's a much more gradual decline. Meanwhile, the electronics still requires 3V and you're supplying 2.4. I don't have datasheets, but I'd imagine that you can't drop very much lower before the whole thing simply fails.
More like, do you have a multicore? Wine is good, but not very efficient. Which might be okay, except he's claiming several background disk intensive processes. A faster disk would likely also help. So now you've got a potentially CPU loaded system trying to juggle disk access in the background. DMA helps, but perhaps it's leading to excessive amounts of locking? As in "well, wine could continue, but it needs access to kernel structure slab which is currently locked until DMA completes".
;)
An easy way to diagnose this is to put up a system monitor that displays, system, user, iowait and idle times. GNOME's system monitor applet does this but has a horrible default iowait color indistinguishable from black. Make it yellow, since it's drastically different than sys or user times
They're also bunk on the voltage: they register 1.2V, as is often the case with rechargables. I picked some up for Wiimote controls, and their usable lifetime is crap. Either the voltage drops below threshold quickly, or the voltage regulator is causing large inefficiencies. For batteries marketed as useful for electronics, I find the shortcoming less than applaudable.
You're thinking about this the wrong way -- on the surface it appears that mturk is an internet labor site, but as you notice, the prices are too low. Mturk provides a framework that both humans and computers can use to solve the same financially interesting problems. Essentially, it provides both incentive to solve problems by hand (though very modest), and a much larger incentive for AI researchers to attack the problem head on, and solve the entire problem set nearly at once. Of course, it does require that the party with the financially motivated problem be willing to disclose it to the world. And there needs to be more publicized case studies of mturk's effectiveness, or even the people who do have such problems won't stop to consider it.
I can't tell whether the current price structure suggests that this has already happened, or that the supply of human intelligence is so vast that it doesn't matter. I do know that several people have written tools to help them solve HITs faster, by grabbing new HITs in the background, and optimizing the display for their needs. But I wonder how much cheaper you could make HITs if you wrote the instructions in Chinese.
They're not, at least not like you're thinking (802.11 security). They're regulating consumer devices and the regulated radio spectrum, and requiring some form of lockout from being able to use consumer equipment to monitor, broadcast or interfere with regulated spectrum. To this end, they've been making decisions on security. The implication here is that the FCC expects some lockdown measures to be done entirely in software. It also suggests that some vendor has already done this. I wonder how much crytographical experience the FCC has in its employees, and how that knowledge was consulted in the decision.
Unfortunately, it also gives creedence to the people suggesting that the FCC regulations require closed source layers.
It's probably too late for my comment to be highly moderated, but really, if you want to be involved in a large and existing project, you have two choices. The first one is to fix bugs. The second way is to write documentation. Some people suggest TODO lists, but those are usually the hard parts that developers intentionally put off until there's nothing else they can feasibly do. What you really want is experience going through the motions of finding code, reading it, evaluating it, suggesting an improvement and following through.
;)
If you're a linux user for some time, I hope you've become accustomed to the practice of filing bugs with your distribution. Pick one that annoys you and decide to fix it. This is a very common way for a user to become a developer: fixing the problems that are important to them. That you haven't done this yet suggests you don't have such a pet bug. Trying to fix someone else's bug is usually painful. First you have to be able to duplicate the problem, then make sure it's a problem with the code, that it's not fixed in CVS, etc.
This is why I suggest that you write or verify documentation, especially man pages. There's numerous advantages to this approach:
* man pages have a standard format that you can learn and follow to guide you
* man pages are a standard tool everyone else uses to find information
* it demonstrates your ability to communicate eloquently in written language
* it requires you to read source code and become familiar with a lot of the body of the code
* your contribution will not be limited by your ability to understand obscure coding mistakes or hardware interactions you can't reproduce
* there are far fewer people writing documentation than fixing bugs
* using the revision history to determine when a feature was added is far simpler than determining when a bug was introduced
* if there's a crazy build system, you won't be required to figure it out, though it would make sense to so you can write about it
Because you've taking a holistic approach to contributing, you'll be one of the few contributers who knows the whole source code. And you'll know so much of functionality that determining which reported bugs are configuration errors versus genuine bugs in code will be easier.
Well, I'm referring more to "Open Source Politics", "Open Source Journalism," or "Open Source Photography" where it's not about software, but very much wants to ride on the Open Source Software boat. It just presses a silly personal button to see the liberal use of the phrase Open Source to denote a certain concept of sharing. Open source isn't just about being able to modify and distribute changes, it's about having access at the same level as the authors to the preferred medium of change, hence the term Source.
;)
It's been a lot better now, that Creative Commons has stepped up to codify a range of intellectual properties not explicitly software. So probably rather than beating someone over the head for Open Source Government, an encouraging letter from the CC would be in order
So is there anything to be done about Open Source works that are not software, and do not have any sense of Source to them at all?
The open source hobbyist nature of mythTV attracts the kind of people who'd rather spec out their own hardware and help tweak the software. But the reason you can't find any for sale is probably because you didn't think to look at the ads.
That would be because Dell is large enough (and smart enough) to eliminate middlemen. They don't build their own laptops, but they do contract to have laptops built explicitly for them, similar to how the OLPC was done. system76 on the other hand, seems to rebrand Acer laptops. I wonder how they'll cope with Dell's entrance. Not well, I imagine.
Market incentives are great, but most people simply don't have access to the data that counts. Sicko covers the incentives program in socialized health care: they do exist, but for different people. Doctors are given incentives to get people to stop smoking, and for the highest percentage of patients arriving for wellness checkups. And the vast majority of the film is dedicated to how HMOs respond to those market pressures: they make more money denying health care than providing it.
We invent new technology, expect to use it, and expect that costs won't rise. Huh? We're expecting to get more for less. That only works for computer hardware. (in a socialist medicine system, quotas and delaying tactics are used to fight this problem)
When costs rise, we don't expect higher than average margins. All the HMOs have experienced major returns recently, and Moore's film mentions this. He doesn't speculate on why, however. Which I think is a bit unfortunate.
The attitude is "I'll pay anything to save my dying children!". We then act all offended that the hospital bill heads toward infinity. Since death is common (100% of your children will die!) you can expect to pay until you can pay no more or until we run out of technology to sell you. (as above, socialist systems deny you this choice)
How much is another six months worth to you personally? How much additional loans would you take out to extend your life by six months (or ten years)? In a free market scenario, you take out as many loans as you can to support yourself and your family to survive. The children of the poor will suffer poor care while the children of the rich will live life to the fullest money can buy. This is a (if not the) fundamental problem with free market health care. Life extending health care's value approaches infinity. All I can say is, your phrasing makes you a bastard, and by your own logic you should kill yourself now to spare the potential expenses you'll incur in living life.
Simple economics is causing all service industries to be relatively more expensive. The factory worker is now more productive because he has huge machines. The high-tech worker is absurdly productive because he only produces digital data which is trivial to replicate. The hospital worker, like the college professor, is not getting such huge productivity increases. Widgets and software can be sold cheaply while still paying the workers well, but hospital services can not be made cheap while paying the workers well. Because everything is relative, hospital costs skyrocket.
So despite the heavy economic incentive currently available, no huge increase in productivity is being found. There's likely a large number of reasons for this, like the definition of productivity, the unintended drug-prohibition side effect of junkies faking illnesses in ERs to get a fix, and a lopsided bargaining table with HMOs. But even if that's all bunk or acceptable, there's still a failure of the market to find inefficiencies.
Over in India, patients have a very limited ability to sue for malpractice and pain and suffering and... Medicine is cheap there....Before a jury, it looks good to have done more intervention.
How on earth does malpractice insurance correlate with the price of medicine? They're two fundamentally different aspects of health care and it's becoming clear you don't understand it. Drug companies in the US defend their pricing strategy as recovering costs. By "costs" they mean "paying universities for their findings, free samples for doctors, and buying large ads telling you to ask your doctor about a specific drug".
Cesearian is in no way a cover your ass maneuver. It correlates with an increased mortality rate, quite sharply. It seems most critics feel this is because the hospital can charge more for a C-section than a normal birth. Recall that at the same time our insurance agencies are booming hospitals are becoming broke. I'd wager a good number is also due to vanity.
Our health insurance is too good at insulating us from the costs of various procedures. We don't shop around for a good deal.
Bullshit. My last insurance had a premium and high deductibles. I'm not about to go shopping for diseases I don't have. Others might (re: drug addictions), but good luck. And if the expensive lot downtown is truly expensive, your HMO probably doesn't have it on its "preferred" list -- their primary legitimate objective is to reduce
For an undergraduate course, your complaints are sound. But at the graduate level, we're faced with a serious problem: the state of the art is so incredibly vast that preparing you to build on the body of existing work takes some time. At some point a grad student needs to be exposed to the papers and difficult problems that people face. Unfortunately, most math classes focus on the same problem set oriented homework instruction, even at the graduate level. It's an important experience to try to solve difficult problems, but as you noted, you had to go outside of class material to discover the solution. Whats worse is that the instructor probably forbade you from looking at such materials, as cheating. What should happen is a standard format of "here's a hard problem, try to prove it". And then present the paper as part of the course. We essentially teach students to ignore the journals they will eventually publish in.
If I might direct your ignorant ass to Amendment 14, it clearly states "All persons born or naturalized in the United States, and subject to the jurisdiction thereof, are citizens of the United States and of the state wherein they reside." Thanks for playing.
As a citizen of Kansas, I would welcome moderate federal regulation of content over the wacknuts who would be inevitably selected to regulate such affairs.
Isn't there a saying that if you have physical access to the device you're already hosed? I guess they can hold themselves to higher standards, but if your laptop has been lost, it's not like I can't rip the chip out or soldier wires to it.
Fuck, have you looked at the firehose? It's no wonder he gets stories posted. He knows grammar and spelling and doesn't get his news from slashdot. Which is better I can say than most submissions.
Nevermind that Dell had a huge surprise earnings announcement. I've seen numerous investors and analyst question Dell's decision to lay off employees, citing their already lean head count to competitors like HP. One analyst suggested that they had gone on a hiring spree lately and perhaps they went overboard. I think your "investors love layoffs" theory is BS. It shows dedication to bring the company back from stagnation, but it's almost impossible to do right and all to often done too late to matter. In this case, I suspect the majority of people cut will be phone sales and service-- Dell seems to be moving into retail outlets, so you HAVE to assume there will be some drop off in direct sales. Five percent in sales, and the rest spread about the business isn't so bad.
But it remains to be seen where and if these cuts happen.
Debian and Ubuntu use buildd. It's not as pretty as the 5 seconds I spent looking at Fedora's tool, but it gets the job done. Ubuntu uses a tool written and run by Canonical, the largest and most integrated sponsor of Ubuntu. It's also closed source, with strange promises that it will be open eventually. That said, launchpad does a hell of a lot more than monitor buildd servers. It's also a far better distro bugtracker than bugzilla is, a project planning tool etc.