I know it's pointless to read the thread you're posting in, but the previously mentioned cystorm unveiled at ISU earlier this year has 3200 cores.
The reason you probably don't see Sun boasting about a lot of its HPC stuff is because it doesn't need to. You don't pick up HPC clients like Cedars-Sinai Hospital, UCLA Neuro Imaging, Wolfram Research, and Sandia National Labs by word of mouth, exactly.
"used to" is absolutely right. One of my partners used to guarantee ie6 compatibility in the contracts until I finally talked her out of it in march or so.
not to mention how useful it is to have two batteries for your phone, so that if one dies, you can swap the other one in without having to find an outlet in an airplane/airport/taxi/commuter train
I don't use pxe, I don't like pxe, i was just pointing out the error in the parent's reasoning. but a bad cable needs the cable replaced: if pxe doesn't pull a valid image it won't reinstall. and your card shouldn't need powercycled since the whole machine just powercycled otherwise the BOOT-TIME pxe wouldn't have activated. as for overwriting grub... what? go read about how pxe works before you start spouting.
pxe network functionality is independent of OS drivers - it's bios level. So if your linux kernel module for your card isn't loading for some reason, a pxe boot will still be able to fetch the "sane" image provided that the cabling or card itself isn't physically malfunctioning.
I think that's only going to be a good thing, because IMO the arguments against pluggable schedulers are weak. "we need the few people working on this to just make the core better for ALL CASES" is about the most valid i've heard, but linux is too broadly applied to force it to meet all cases. realtime, embedded, servers, desktop: i just don't think one scheduler can be shoehorned to maximize performance for all those. You wind up with a crippled scheduler that really only achieves maximum performance in at most one of those four domains. And the question of there being enough developer minds working on it? you can bet that more commercial enterprise will start throwing money at it when they can customize it for their domain.
It's like the dynamic syscall argument in a way. without dynamic syscalls, the argument goes, all the 'fringe functionality' people have to think harder and have to integrate their stuff into the current syscalls/drivers/subsystems. (apologies ingo) however, without dynamic syscalls, all the "middle of the road" functionality people like hardware manufacturers, are unwilling to release drivers that they essentially have to ask customers to compile as a supported option.
Both, IMO are cases of cutting off your leg to spite your foot.
but you could say the same about the Chrome developers
Ahem. Chrome was based on webkit which was derived from the Konqueror browser for KDE. Maybe not a huge market share but probably in the hundreds of thousands of users globally at the time.
and I guess we could say the same about Firefox..
Firefox was based on mozilla which was the open sourced version of the venerable and at one time market-dominating Netscape Navigator.
No, it doesn't matter if the browser has useful features to YOU. it matters if they are useful to someone. And apparently someone out there wanted a modular browser with vi keybindings out there bad enough to write the damn thing. If it's not for you? Don't use it.
Linux should be trying to optimize for hardware, too, right?
I think you misunderstand the problem. ACPI is the power management standard that all the manufacturers use. It's not a particularly good standard in the first place, and in the second place, most manufacturers make horribly broken non-spec ACPI interfaces. They fail to document them adequately if at all. They then provide customized windows drivers for that broken implementation.
Kernel devs are constantly tweaking the ACPI drivers for all the different hardware out there, but they're at a stark disadvantage.
But on the whole, it doesn't really seem like most "Linux geeks" are particularly interested in things like battery life
Between 2.6.29 and 2.6.30, a span of 78 days saw 7 commits to the ACPI subsystem, for a total of about 800 lines of code added. That's pretty average on a size-per-size basis across the rest of the kernel, and normal for the overall upward trend in kernel development speed. So it seems that just as many "linux geeks" (which i am interepreting strictly to mean kernel developers) care about battery life as care about any other drivers short of network, sound and v4l.
(or, as someone posted in the xkcd comic, full screen flash video... which I realize is also at least partially an Adobe issue..
comics are reliable sources of information aren't they. it is ENTIRELY an adobe issue, however fullscreen flash video has worked fine on linux for 3 or 4 years now.
they already cant turn you away if you are unable to pay
Well that's not entirely true. They are in fact only obligated to provide stabilizing care for actual emergencies by the 1986 patient dumping law. Anything chronic is generally out.
I've met a few people that go there for anything, on the public's tab.
That's not exactly how it works. The government doesn't reimburse the hospital for patients who come into the ER but have no insurance. The hospital bills the patient. The patient either pays the bill or it goes to collections. If it goes to collections, and eventually the patient does pay, chances are the hospital will only see 25% of that money. The cost to the hospital of "ER Abuse" is distributed across the rest of the hospital and passed on to insurers and eventually gets paid by policy holders. So you're right to imply that the public is still picking up the tab, it's just only the insured, and not all taxpayers who shoulder that particular burden.
I would be shocked if Obama signs any bill, or at least any bill that actually has teeth, which puts a national cap on damages awarded at lawyerpoint.
I too, would be shocked. but again I'm not entirely sure that the definition of tort reform you're employing (which is the one usually tossed around by republicans) is the one we ought to be using.
Malpractice insurance, on the other hand, represents an awfully large slice of the pie in a doctor's office. Perhaps we need a public option for that too.
Do you know how much goes into the medical system? How many people are employed and what they do? You can't cut any of them out.
Except for the insurers. Sure they take a risk, but they've actually calculated nearly all of the risk out of the equation. They're really just a high-interest credit card that you pay on before you spend the money, which can turn around and tell you that you've exceeded your limit before you've spent a dime.
One of the easily and often over looked problems with universal health care, is that there is literally nobody to give it.
Which is why a good bill would do the old education-for-work exchange. Your med school is free if you spend X years working for lower wages in approved clinics.
We're not going to fix it with preventive medicine
Nobody said that we are. But preventive care cuts the total costs associated with health care. Preventive is a small part of a larger picture.
Spreading out the cost sounds great until you realize that a lot of people don't have insurance because they can't afford it, and won't be paying their full share if they go for a public option either,
Lots of people don't have coverage (including medicare/medicaid) now, and you still pay for it. You pay more because they are not already part of a plan and recieving preventive care as they need it. You pay when the hospital gets stuck with an unpaid bill because costs go up to cover it. You pay more for your insurance because of this.
but this is beside the point because "public option" is not the same as "expanded medicaid." It means you will have a government-funded private institution providing health insurance that is subsidized by tax dollars. It is competition for the status-quo insurers and can be run in such as way as to be pretty close to cost neutral. The public option will bring all individuals and small business' net health care spending (including insurance costs and medicare/medicaid taxes) down. Some other provisions of the house bill add to the tax burden so I can't say the whole proposal is tax neutral. But there's no downside to the public option
He could have started small and been successful but he bit off more than he could chew.
He repeatedly said throughout the campaign that one of his major 1st year issues was going to be health care reform, and outlined most of what has transpired here. If you voted for him because you listened to him during the election, you should have known this was coming.
I also fundamentally disagree that he should have "started small" because it's not like we have a lot of time to dick around with this. The last time major healthcare reform happened in the US was over 40 years ago. The time to make big changes is now, and no matter if he had gone big or small, the other side of the aisle was going to make it ugly for him.
Lack of government healthcare != able to get help.
Right. We all remember Bush's answer to the healthcare crisis: let them go to the emergency room. ER care is significantly more expensive than proper preventive and general practice care.
It simply means that things are more expensive for those without healthcare in the short term if they need it.
Right. 62% of all personal bankruptcies in the U.S. in 2007 were caused by health problems and 78% of those filers had insurance.
Citation
That doesn't just make things more expensive for those with healthcare, it makes them more expensive for policy holders, anyone who wants a loan, small businesses, investors, and stockholders. And it's not just over the short term, it has an overall detrimental effect on our nation's economic well being which continues to mount.
In general there are a lot of "reactionary" people here in the US who will go to the doctor for -anything-, heck, wasn't it just a few years ago where because of the prevalence of people geoing to the doctors for every little thing was going to create more drug resista lnt illnesses?
it's not people going to the doctors that causes drug resistance, it's the repeated treatment of the same bacterial infections with a broad spectrum of antibiotics. This has a lot to do with tort liability, a subject I'm not as well versed on as I would like to be. I do think that tort reform should be a part of any comprehensive medical reform, but I think that we have to be careful.
In general, if it makes someone sick with obvious symptoms, they are going to get help here in the US. Its just the common reaction, not sure about in other countries (the US is the only country I've lived in for an extended period of time, though I have traveled to many different countries) but in the USA, a lot of people go to the doctor or even the emergency room for every thing.
"in general" is a stretch in this case. Lots of conditions can't be taken care of in an emergent care setting. This may be true for broken limbs, allergic reactions, and like conditions, but it doesn't address the situation with regard to chronic conditions, diabetes, cancer, and so on. This is the situation that most urgently needs to be addressed. If there was a law like the 1986 "patient dumping" law that applied to chronic care as well as ERs it would cost the medical industry billions. as is they are only required to "stabilize." and then they can ask for your insurance card and or show you the door.
spreadsheet... worst answer ever. I agree with the ID (we used asset tags) but a SPREADSHEET? all it takes is one moron and the sort function to screw up your system permanently.
Databases really aren't that hard.
Please let me know of any bigger claimed value.
I know it's pointless to read the thread you're posting in, but the previously mentioned cystorm unveiled at ISU earlier this year has 3200 cores.
The reason you probably don't see Sun boasting about a lot of its HPC stuff is because it doesn't need to. You don't pick up HPC clients like Cedars-Sinai Hospital, UCLA Neuro Imaging, Wolfram Research, and Sandia National Labs by word of mouth, exactly.
"used to" is absolutely right. One of my partners used to guarantee ie6 compatibility in the contracts until I finally talked her out of it in march or so.
sshd running by default? are you mad?
not to mention how useful it is to have two batteries for your phone, so that if one dies, you can swap the other one in without having to find an outlet in an airplane/airport/taxi/commuter train
http://www.linux.org/apps/AppId_644.html
I don't use pxe, I don't like pxe, i was just pointing out the error in the parent's reasoning. but a bad cable needs the cable replaced: if pxe doesn't pull a valid image it won't reinstall. and your card shouldn't need powercycled since the whole machine just powercycled otherwise the BOOT-TIME pxe wouldn't have activated. as for overwriting grub... what? go read about how pxe works before you start spouting.
pxe network functionality is independent of OS drivers - it's bios level. So if your linux kernel module for your card isn't loading for some reason, a pxe boot will still be able to fetch the "sane" image provided that the cabling or card itself isn't physically malfunctioning.
I think that's only going to be a good thing, because IMO the arguments against pluggable schedulers are weak. "we need the few people working on this to just make the core better for ALL CASES" is about the most valid i've heard, but linux is too broadly applied to force it to meet all cases. realtime, embedded, servers, desktop: i just don't think one scheduler can be shoehorned to maximize performance for all those. You wind up with a crippled scheduler that really only achieves maximum performance in at most one of those four domains. And the question of there being enough developer minds working on it? you can bet that more commercial enterprise will start throwing money at it when they can customize it for their domain.
It's like the dynamic syscall argument in a way. without dynamic syscalls, the argument goes, all the 'fringe functionality' people have to think harder and have to integrate their stuff into the current syscalls/drivers/subsystems. (apologies ingo) however, without dynamic syscalls, all the "middle of the road" functionality people like hardware manufacturers, are unwilling to release drivers that they essentially have to ask customers to compile as a supported option.
Both, IMO are cases of cutting off your leg to spite your foot.
I smell another LKML flamewar coming....
but you could say the same about the Chrome developers
Ahem. Chrome was based on webkit which was derived from the Konqueror browser for KDE. Maybe not a huge market share but probably in the hundreds of thousands of users globally at the time.
and I guess we could say the same about Firefox..
Firefox was based on mozilla which was the open sourced version of the venerable and at one time market-dominating Netscape Navigator.
No, it doesn't matter if the browser has useful features to YOU. it matters if they are useful to someone. And apparently someone out there wanted a modular browser with vi keybindings out there bad enough to write the damn thing. If it's not for you? Don't use it.
Does this mean racing games will have to use some kind of different pickups for speed boosts?
David Sedaris had a great line about Europe in Naked
"Watch out, he's been to europe... he might judge us!"
that wooshing sound you hear? That's a perfectly good joke blowing right over your head.
How difficult would it have been to give the guy a temporary ID or to simply ask what his business on the place was and then corroborate his history
or, call me crazy, just leave him alone if he wasn't doing anything wrong?
Linux should be trying to optimize for hardware, too, right?
I think you misunderstand the problem. ACPI is the power management standard that all the manufacturers use. It's not a particularly good standard in the first place, and in the second place, most manufacturers make horribly broken non-spec ACPI interfaces. They fail to document them adequately if at all. They then provide customized windows drivers for that broken implementation.
Kernel devs are constantly tweaking the ACPI drivers for all the different hardware out there, but they're at a stark disadvantage.
But on the whole, it doesn't really seem like most "Linux geeks" are particularly interested in things like battery life
Between 2.6.29 and 2.6.30, a span of 78 days saw 7 commits to the ACPI subsystem, for a total of about 800 lines of code added. That's pretty average on a size-per-size basis across the rest of the kernel, and normal for the overall upward trend in kernel development speed. So it seems that just as many "linux geeks" (which i am interepreting strictly to mean kernel developers) care about battery life as care about any other drivers short of network, sound and v4l.
(or, as someone posted in the xkcd comic, full screen flash video... which I realize is also at least partially an Adobe issue..
comics are reliable sources of information aren't they. it is ENTIRELY an adobe issue, however fullscreen flash video has worked fine on linux for 3 or 4 years now.
they already fixed it. BORING!
Is the white guy they shopped in a lookalike for mitt romney or is that my imagination?
I've been runing X on linux since 1995!
Well then quite frankly you must be fucking blind not to see it at the top of Ubuntu's own front page.
netbook remix != laptop install. Derisiveness fail.
they already cant turn you away if you are unable to pay
Well that's not entirely true. They are in fact only obligated to provide stabilizing care for actual emergencies by the 1986 patient dumping law. Anything chronic is generally out.
I've met a few people that go there for anything, on the public's tab.
That's not exactly how it works. The government doesn't reimburse the hospital for patients who come into the ER but have no insurance. The hospital bills the patient. The patient either pays the bill or it goes to collections. If it goes to collections, and eventually the patient does pay, chances are the hospital will only see 25% of that money. The cost to the hospital of "ER Abuse" is distributed across the rest of the hospital and passed on to insurers and eventually gets paid by policy holders. So you're right to imply that the public is still picking up the tab, it's just only the insured, and not all taxpayers who shoulder that particular burden.
I would be shocked if Obama signs any bill, or at least any bill that actually has teeth, which puts a national cap on damages awarded at lawyerpoint.
I too, would be shocked. but again I'm not entirely sure that the definition of tort reform you're employing (which is the one usually tossed around by republicans) is the one we ought to be using.
Malpractice insurance, on the other hand, represents an awfully large slice of the pie in a doctor's office. Perhaps we need a public option for that too.
Do you know how much goes into the medical system? How many people are employed and what they do? You can't cut any of them out.
Except for the insurers. Sure they take a risk, but they've actually calculated nearly all of the risk out of the equation. They're really just a high-interest credit card that you pay on before you spend the money, which can turn around and tell you that you've exceeded your limit before you've spent a dime.
One of the easily and often over looked problems with universal health care, is that there is literally nobody to give it.
Which is why a good bill would do the old education-for-work exchange. Your med school is free if you spend X years working for lower wages in approved clinics.
We're not going to fix it with preventive medicine
Nobody said that we are. But preventive care cuts the total costs associated with health care. Preventive is a small part of a larger picture.
Spreading out the cost sounds great until you realize that a lot of people don't have insurance because they can't afford it, and won't be paying their full share if they go for a public option either,
Lots of people don't have coverage (including medicare/medicaid) now, and you still pay for it. You pay more because they are not already part of a plan and recieving preventive care as they need it. You pay when the hospital gets stuck with an unpaid bill because costs go up to cover it. You pay more for your insurance because of this.
but this is beside the point because "public option" is not the same as "expanded medicaid." It means you will have a government-funded private institution providing health insurance that is subsidized by tax dollars. It is competition for the status-quo insurers and can be run in such as way as to be pretty close to cost neutral. The public option will bring all individuals and small business' net health care spending (including insurance costs and medicare/medicaid taxes) down. Some other provisions of the house bill add to the tax burden so I can't say the whole proposal is tax neutral. But there's no downside to the public option
He could have started small and been successful but he bit off more than he could chew.
He repeatedly said throughout the campaign that one of his major 1st year issues was going to be health care reform, and outlined most of what has transpired here. If you voted for him because you listened to him during the election, you should have known this was coming.
I also fundamentally disagree that he should have "started small" because it's not like we have a lot of time to dick around with this. The last time major healthcare reform happened in the US was over 40 years ago. The time to make big changes is now, and no matter if he had gone big or small, the other side of the aisle was going to make it ugly for him.
Lack of government healthcare != able to get help.
Right. We all remember Bush's answer to the healthcare crisis: let them go to the emergency room. ER care is significantly more expensive than proper preventive and general practice care.
It simply means that things are more expensive for those without healthcare in the short term if they need it.
Right. 62% of all personal bankruptcies in the U.S. in 2007 were caused by health problems and 78% of those filers had insurance. Citation That doesn't just make things more expensive for those with healthcare, it makes them more expensive for policy holders, anyone who wants a loan, small businesses, investors, and stockholders. And it's not just over the short term, it has an overall detrimental effect on our nation's economic well being which continues to mount.
In general there are a lot of "reactionary" people here in the US who will go to the doctor for -anything-, heck, wasn't it just a few years ago where because of the prevalence of people geoing to the doctors for every little thing was going to create more drug resista lnt illnesses?
it's not people going to the doctors that causes drug resistance, it's the repeated treatment of the same bacterial infections with a broad spectrum of antibiotics. This has a lot to do with tort liability, a subject I'm not as well versed on as I would like to be. I do think that tort reform should be a part of any comprehensive medical reform, but I think that we have to be careful.
In general, if it makes someone sick with obvious symptoms, they are going to get help here in the US. Its just the common reaction, not sure about in other countries (the US is the only country I've lived in for an extended period of time, though I have traveled to many different countries) but in the USA, a lot of people go to the doctor or even the emergency room for every thing.
"in general" is a stretch in this case. Lots of conditions can't be taken care of in an emergent care setting. This may be true for broken limbs, allergic reactions, and like conditions, but it doesn't address the situation with regard to chronic conditions, diabetes, cancer, and so on. This is the situation that most urgently needs to be addressed. If there was a law like the 1986 "patient dumping" law that applied to chronic care as well as ERs it would cost the medical industry billions. as is they are only required to "stabilize." and then they can ask for your insurance card and or show you the door.
spreadsheet... worst answer ever. I agree with the ID (we used asset tags) but a SPREADSHEET? all it takes is one moron and the sort function to screw up your system permanently. Databases really aren't that hard.