It doesn't cost anything to let independently unviable fetuses prematurely delivered into the world die and try again. That would be a million dollars that could have gone into research to prevent miscarriages and premature births [...]
This is what we thought, until she started coming up with her own examples and further deductions. I'm not guaranteeing that she will always think before doing stuff of course -- heck, I didn't, even when I was well into the adulthood;)
I agree with you, but your suffocation-in-a-bag example is poorly chosen. It's infants and toddlers that suffocate with plastic bags, they often have too little manipulative skills to free themselves, or they don't comprehend cause-and-effect enough. Those warnings are really there to beat the "obvious" into the clueless parents/caregivers. Hard to blame the kid for sticking with stupid parents/sitters at that age.
Good judgement and common sense are learned abilities. You let your 7 y.o. roam wild with no feedback from parents, and he/she will end up with trauma. No shit, what did you expect.
I agree. We never had a problem with our daughter and household chemicals. She figured out how to open childproof kitchen cabinet locks when she was ~14 months old. Took her 20 minutes, apparently. We have been repeatedly instructing her as to why it's a bad idea to play with those things you find there, and what happens when you swallow some -- including showing pictures of perforated stomachs. Then I managed to get some pig stomachs to see what HCl-containing toilet cleaner did to them. She doesn't do a lot of silly stuff because she knows exactly what's going to happen to her if she would. You run across the street? -- here's some compound fracture pics to see and learn from. Easy as cake. We abhor unsubstantiated rules, and at age 6 she does understand the reasoning for most of the things we expect of her. Including that some rules are simply social constructs adhered to from respect to others.
You've got your scale way off. Lifetime institutionalization, my ass. $300,000 is what it'd cost for a kid to stay at a hospital ward here in the U.S. for one month, with a "simple" surgery or two in the meantime. $1M for a NICU stay for 3 months -- I've seen the bills.
Any sort of a realistic chemical simulation that could do very basic college-level chemistry would require a big-ass data center just to crunch the numbers. So it's not really feasible. You can simulate certain limited scenarios, but for a lab simulation where you can just play with things and see what transpires -- we're a few centuries away from that I'd say.
No one can "pull data" off a modern hard drive after you overwrite it just once. Stop believing in fairytales.
As for analog recordings -- with audio recordings that were erased once but not overwritten, you can usually make out words. With video, whatever quality is left is so poor that even a 3rd gen copy from that will look better.
Worse yet, this all starts with school and parents, at an early age. You tell your kid "don't ask stupid questions" or "because it is so" once too many times, and they learn for you to turn rationality off. Then they grow up believing all sorts of crap.
I should have been clearer: the insurer got the hospital to slash the bill by half, then they paid ~$400k, leaving $100k to be paid out of pocket (10% of the original bill).
My friends had a son that was born 2+ months premature and he had to spend ~3 months in the NICU.
The bill sent to the insurance company was on the order of $1M. And that was really on a lower end, at about $12k per day. Had he had more surgeries, it'd be more like $20k per day, on average, or so I'm told.
Due to various agreements insurers have with hospitals, they ended up covering almost half of that. Friends were left with, oh well, about $100k to pay out of pocket. This amount of money generally buys you small house where they live.
I'm not saying "be able to kill a child", but one has a choice: treat the kid no matter what the cost, or just let go. If I knew I'd face a bill of that magnitude, I'd say "well, sorry, we'll need to [have|adopt] another one instead". The fact that "modern medicine" can cope with a lot of things doesn't mean that you have to bankrupt yourself. Maybe "modern medicine" needs to grow legs and figure out how to shed costs. By an order of magnitude, give or take.
It's slightly ridiculous that an outpatient laparoscopic surgery that takes maybe 50 minutes in all, would be billed for $12k. Or that a delivery would be billed for $30k.
So you say you pay all the costs out of pocket? Because your argument just flies in face of how insurance works. The more the insurer has to spend, the higher the rates for everyone, not just you.
The problem is that infant mortality is not counted the same in every country. So those figures are probably meaningless with a detailed explanations of how they were collected.
It's not a genetic condition that we are aware of. It'll take a few more centuries to positively state that premature births have no underlying genetic factors.
Oh yeah, my daughter had croup too. On top of undiagnosed respiratory allergies. 't was no fun at the time. We eventually switched her pediatrician, now we go to a tiny office where you never wait longer than 5 minutes, and where if you call in they can see you in an hour. Now expecting our 2nd one, 2 more months to go.
Methinks a lot of that meteorite's kinetic energy will be tranformed into heat almost instantly upon impact, vaporizing a lot of stuff. It's the blast -- the heat-induced expansion of atmosphere and vaporized material that will create most damage methinks.
I'd say there's another problem: that oo.org, inkscape and scribus ALL use different application development frameworks. This means that developers are not portable. Once someone is fluent in oo.org, it'd take another year to become fluent in gtk, and perhaps less in Qt. This methinks bleeds manpower: you can't be as flexible as you could potentially be, and you can only contribute to one class of projects:
- oo.org uses GSL: their own framework - inkscape uses glib/GTK - scribus uses Qt
Now, my personal preference would be to port everything to Qt. But this has a couple problems. First of all, it'd need to have Nokia on board, as Qt would really be shaken down by porting something as big as oo.org to it. Nokia would need to supply badly needed bugfixes and new development resources for Qt to make oo.org porting possible.
Porting to GTK is harder, since generally you write way more code to accomplish anything in GTK, compared to Qt. At least there's way more unfunny boilerplate to write.
As for the oo.org's framework -- I have no clue. There is no real documentation for it, and there are probably very few people outside of core developer group who know anything substantial about it. Neooffice.org's pluby knows it well, but that's rare.
To do anything implies porting. I've recently looked at Inkscape's codebase -- it's pretty much married to glib. Porting it to oo.org's framework is probably a man-year to complete. And you'd better start with good understanding of oo.org's framework first.
Not quite. You still want to verify the submission: make sure that the submitter stands by their words. If they do, but your checking shows that they lied, you have a double whammy. So GP is half-right.
Slashdot Mirror
It doesn't cost anything to let independently unviable fetuses prematurely delivered into the world die and try again. That would be a million dollars that could have gone into research to prevent miscarriages and premature births [...]
That. Thank you.
Consider yourself lucky, then? I mean, what can I say short of scanning the bills and posting them somewhere?
This is what we thought, until she started coming up with her own examples and further deductions. I'm not guaranteeing that she will always think before doing stuff of course -- heck, I didn't, even when I was well into the adulthood ;)
I guess I agree, then.
I agree with you, but your suffocation-in-a-bag example is poorly chosen. It's infants and toddlers that suffocate with plastic bags, they often have too little manipulative skills to free themselves, or they don't comprehend cause-and-effect enough. Those warnings are really there to beat the "obvious" into the clueless parents/caregivers. Hard to blame the kid for sticking with stupid parents/sitters at that age.
Good judgement and common sense are learned abilities. You let your 7 y.o. roam wild with no feedback from parents, and he/she will end up with trauma. No shit, what did you expect.
I agree. We never had a problem with our daughter and household chemicals. She figured out how to open childproof kitchen cabinet locks when she was ~14 months old. Took her 20 minutes, apparently. We have been repeatedly instructing her as to why it's a bad idea to play with those things you find there, and what happens when you swallow some -- including showing pictures of perforated stomachs. Then I managed to get some pig stomachs to see what HCl-containing toilet cleaner did to them. She doesn't do a lot of silly stuff because she knows exactly what's going to happen to her if she would. You run across the street? -- here's some compound fracture pics to see and learn from. Easy as cake. We abhor unsubstantiated rules, and at age 6 she does understand the reasoning for most of the things we expect of her. Including that some rules are simply social constructs adhered to from respect to others.
You've got your scale way off. Lifetime institutionalization, my ass. $300,000 is what it'd cost for a kid to stay at a hospital ward here in the U.S. for one month, with a "simple" surgery or two in the meantime. $1M for a NICU stay for 3 months -- I've seen the bills.
That's real insight, inviolet. Thank you!
Any sort of a realistic chemical simulation that could do very basic college-level chemistry would require a big-ass data center just to crunch the numbers. So it's not really feasible. You can simulate certain limited scenarios, but for a lab simulation where you can just play with things and see what transpires -- we're a few centuries away from that I'd say.
No one can "pull data" off a modern hard drive after you overwrite it just once. Stop believing in fairytales.
As for analog recordings -- with audio recordings that were erased once but not overwritten, you can usually make out words. With video, whatever quality is left is so poor that even a 3rd gen copy from that will look better.
Worse yet, this all starts with school and parents, at an early age. You tell your kid "don't ask stupid questions" or "because it is so" once too many times, and they learn for you to turn rationality off. Then they grow up believing all sorts of crap.
I should have been clearer: the insurer got the hospital to slash the bill by half, then they paid ~$400k, leaving $100k to be paid out of pocket (10% of the original bill).
The problem isn't really "a bit of money".
My friends had a son that was born 2+ months premature and he had to spend ~3 months in the NICU.
The bill sent to the insurance company was on the order of $1M. And that was really on a lower end, at about $12k per day. Had he had more surgeries, it'd be more like $20k per day, on average, or so I'm told.
Due to various agreements insurers have with hospitals, they ended up covering almost half of that. Friends were left with, oh well, about $100k to pay out of pocket. This amount of money generally buys you small house where they live.
I'm not saying "be able to kill a child", but one has a choice: treat the kid no matter what the cost, or just let go. If I knew I'd face a bill of that magnitude, I'd say "well, sorry, we'll need to [have|adopt] another one instead". The fact that "modern medicine" can cope with a lot of things doesn't mean that you have to bankrupt yourself. Maybe "modern medicine" needs to grow legs and figure out how to shed costs. By an order of magnitude, give or take.
It's slightly ridiculous that an outpatient laparoscopic surgery that takes maybe 50 minutes in all, would be billed for $12k. Or that a delivery would be billed for $30k.
So you say you pay all the costs out of pocket? Because your argument just flies in face of how insurance works. The more the insurer has to spend, the higher the rates for everyone, not just you.
The problem is that infant mortality is not counted the same in every country. So those figures are probably meaningless with a detailed explanations of how they were collected.
It's not a genetic condition that we are aware of. It'll take a few more centuries to positively state that premature births have no underlying genetic factors.
Oh yeah, my daughter had croup too. On top of undiagnosed respiratory allergies. 't was no fun at the time. We eventually switched her pediatrician, now we go to a tiny office where you never wait longer than 5 minutes, and where if you call in they can see you in an hour. Now expecting our 2nd one, 2 more months to go.
Methinks a lot of that meteorite's kinetic energy will be tranformed into heat almost instantly upon impact, vaporizing a lot of stuff. It's the blast -- the heat-induced expansion of atmosphere and vaporized material that will create most damage methinks.
Forgot to add the Novell's go-oo people the the list of folks who know oo.org, of course.
I'd say there's another problem: that oo.org, inkscape and scribus ALL use different application development frameworks. This means that developers are not portable. Once someone is fluent in oo.org, it'd take another year to become fluent in gtk, and perhaps less in Qt. This methinks bleeds manpower: you can't be as flexible as you could potentially be, and you can only contribute to one class of projects:
- oo.org uses GSL: their own framework
- inkscape uses glib/GTK
- scribus uses Qt
Now, my personal preference would be to port everything to Qt. But this has a couple problems. First of all, it'd need to have Nokia on board, as Qt would really be shaken down by porting something as big as oo.org to it. Nokia would need to supply badly needed bugfixes and new development resources for Qt to make oo.org porting possible.
Porting to GTK is harder, since generally you write way more code to accomplish anything in GTK, compared to Qt. At least there's way more unfunny boilerplate to write.
As for the oo.org's framework -- I have no clue. There is no real documentation for it, and there are probably very few people outside of core developer group who know anything substantial about it. Neooffice.org's pluby knows it well, but that's rare.
To do anything implies porting. I've recently looked at Inkscape's codebase -- it's pretty much married to glib. Porting it to oo.org's framework is probably a man-year to complete. And you'd better start with good understanding of oo.org's framework first.
Not quite. You still want to verify the submission: make sure that the submitter stands by their words. If they do, but your checking shows that they lied, you have a double whammy. So GP is half-right.
University PR departments are usually below par, and sometimes they must be hiring people fired from tabloids, it seems.
Because surely just basing it on those videos you can judge the wing twist and such. LOL.