Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

> Ever look up how respected skepticism is within the larger philosophical community?

I'm a little unclear on what point you're trying to make here. Can you clarify?

> I mean look at my pastebin post: http://pastebin.com/cniysd82

I took a look at your pastebin post. There are a lot of criticisms there of various kinds of bad practices, but not all of them have anything to do with whether the medicines actually work. For instance, the patent issue; while that's a fair issue in its own right, whether large pharmaceutical companies can prevent people from making generic equivalents by using patents does not affect whether the drug works or not. Or direct to consumer advertising; again, it may be a bad idea, but it doesn't have anything to do with whether the drugs actually work.

Many of the other criticisms here are fairly hypothetical. Yes, there are places where the system isn't ideal, where there's potential for the wrong incentives. There are places where it would be nice to do research that covered a broader spectrum. But that doesn't mean that it's all invalid. We live in an imperfect world. We should try to fight those cases when we can, try to get better results, but you shouldn't write off the entire industry merely because it's imperfect.

Here's another example. In the software industry, I see bad practices all the time. People not writing unit tests, not doing full regression tests, writing sloppy code that doesn't handle all of the error conditions, and so on. And yet, somehow, we manage to get by. Software generally works, it does what it says, it improves whatever it was setting out to improve. Sure, there are some big expensive failures you can point to. Sure, it would be nice if we did a better job at this, and should try to continue to fight for higher quality software. But just because there is some software imperfectly written doesn't mean that you should just write off the software industry.

> But does SBM actually address any of the criticism? Not a single point of it, because there is no defense; in fact, it's all coming from high-level 'insiders' in the medical community -- JAMA, NEJM, the IOM, etc.

Really? I just decided to take a look at SBM; I wasn't familiar with it before this thread, but decided to take a look at it. Here's an article on reducing prescriptions for elderly patients, because they may do more harm than good: http://www.sciencebasedmedicine.org/index.php/how-do-we-avoi... (addressing one of your concerns about differences in how medications effect the elderly). Or here's an example where they do address one of the concerns that you mention; they demonstrate that doctors actually are more skeptical of research funded by the pharmaceutical industry: http://www.sciencebasedmedicine.org/index.php/news-flash-doc....

> Instead they just spin it in order to trick people who are predisposed to have faith in modern medicine. (And I use the term faith, because if you're familiar with these issues then it's unmistakably clear that this is really what it is.)

You know, I do tend to be skeptical of pharmaceutical remedies, and so try to minimize them myself. But to say that you have to have faith to buy into modern medicine is a bit of a stretch. How do you explain ever increasing life expectancies? Clearly, there is something going right in modern medicine.

> What science-based medicine does (again, the blog, not the concept) is really no different than what the evangelical megachurches do, it's just dressed up in different language.

Citing actual scientific studies, which may be flawed in certain ways, is the same as merely preaching mythology from a 2000 year old book based on no science whatsoever? Remember, "science" is not some binary thing, where if there's one flaw, it's all false. It's a process, by which we attempt to come up with better models of the world, and try to reduce bias in the process. Sometimes there will still be some bias; you won't necessarily be able to eliminate it all. But that doesn't mean it's worthless.

There are definitely a lot of ways in which I wish that pharmaceutical research would be improved; but the fact that there are people now who are living perfectly normal lives while HIV positive with anti-retroviral therapies, when just 10 or 20 years ago they would have died of the same disease, leads me to believe that it's not all bad. I wish those drugs were cheaper, that they weren't so tied up with patents, and so on; but you know, I wish I had a pony too. To equate the research and development that went into such life-saving measures as equivalent to an evangelical megachurch is quite frankly ridiculous.


"not all of them have anything to do with whether the medicines actually work."

That's because in general I'm only interested in systemic problems, not specific case studies. There are entire books written about just anti-depressants, or statins, or whatever, which you can easily find on Amazon.

"How do you explain ever increasing life expectancies?"

Of the 30-year increase in life expectancy over the last 100 years, 25 years has come from better public health (e.g. sanitation), and another 1.5 years has come from preventive care like vaccination.

Source: Bunker JP, Frazier HS, Mosteller F. Improving health: measuring effects of medical care. Milbank Quarterly 1994;72:225-58.


lambda asked the same question I had, which is, simply: what is the point you're trying to make? You're making a lot of side comments about minor points, but I'm not sure what your thesis is.


> That's because in general I'm only interested in systemic problems, not specific case studies. There are entire books written about just anti-depressants, or statins, or whatever, which you can easily find on Amazon.

What is the point that you are trying to prove? Are you merely trying to demonstrate that there are certain systemic problems? If so, then congrats, you've won, there are some systemic problems. I don't think there has ever been a wide-scale system involving humans that hasn't had a certain amount of cheating, lying, corruption, and the like. If someone tried to claim to me that there was an entire multi-trillion dollar industry that did not involve some amount of cheating, lying, and corruption, I would laugh in their face.

Are you trying to argue that the pharmaceutical industry has a net negative value; that it it something that causes more harm than good? Because that's going to be a lot harder to prove, and a bunch of little anecdotes does not make a good argument.

You seem to be fairly concerned with certain people, who discuss science based medicine, and say that they are corrupt because they advocate for modern pharmaceuticals and criticize certain alternative medicine. Your evidence seems to be that they do not talk about all of the corruption and problems that you would like them to talk about. Do you have anything more than that?

> Of the 30-year increase in life expectancy over the last 100 years, 25 years has come from better public health (e.g. sanitation), and another 1.5 years has come from preventive care like vaccination. > > Source: Bunker JP, Frazier HS, Mosteller F. Improving health: measuring effects of medical care. Milbank Quarterly 1994;72:225-58.

Hmm. That's an 18 year old source, talking about life expectancy, which is a trailing indicator. So, 25 years of life expectancy from better public health (like sanitation and nutrition) is an amazing thing. And you say that 1.5 years come from preventative care like vaccination, and dismiss the other 3.5 years. Now, 3.5 years may not sound like much out of about 75. But think about it for a bit. 3.5 years is averaged across the whole population. Not everyone has a condition that is treatable; many people die of old age, accidents, murder, suicide, and things that modern medicine has not yet made much progress in. Those 3.5 years don't really affect any of those folks. So lets say that 1 in 10 people have a treatable condition (I'm pulling this number out of my ass, by the way; this is just a hypothetical, and the numbers may differ, in which case you would scale the reasoning appropriately). That means that those 1 in 10 people have gained 35 years of their life from medicine. Look around at your family and closest friends. How much would you trade for 35 more years with one of them?

So, you are discounting 18 years of medical progress, as well as treating a few years of life expectancy gained as no big deal. And of course, any talk of life expectancy also ignores quality of life issues; curing something that would have been crippling but not deadly doesn't substantially affect life expectancy, but does affect quality of life.

It sounds like you are trying to argue against the value of modern medicine, which is going to be a tough thing to convince people of, given all of the demonstrable benefits it has. I can understand discussing specific criticisms, and trying to figure out how we can improve it, and that saying "all medicine is scientific progress and is great" is fallacious, but trying to prove that modern medicine has a net negative value because of a few issues of systemic corruption is not the way to do it.


> What is the point that you are trying to prove?

I was arguing against the following statement: "But it's an exaggeration [...] to say that the enterprises that develop new drugs for prescribed medical treatment are corrupt in general beyond what Goldacre claims with specific evidence."

Or, more generally, reminding people why it is that our infrastructure is falling apart and why the federal government is at risk of collapse in the next few years, which are both in large part due to the massive amounts of fraud in the medical system. At least a third of all medical spending is waste and fraud, and that's not even counting the damages from all the needless harm it inflicts on people. Even just fixing some of the low-hanging fruit would leave us with enough money to provide healthcare to all Americans, as well as build an entire nationwide highspeed rail network every single year.

> Your evidence seems to be that they do not talk about all of the corruption and problems that you would like them to talk about.

It's mostly the intellectual dishonesty in virtually every single post that bothers me. The entire point of the blog is to 'prove' that alternative medicine is inferior to mainstream medicine because it isn't supported by science. They do this by looking at all the ways alternative medicine isn't supported by science, while completely sweeping under the rug all of the ways that mainstream medicine isn't supported by science. My concern isn't that the authors aren't mentioning specific issues, but rather that they're going out of their way to mislead their readers about the issues and the state of medicine more generally.

> That's an 18 year old source, talking about life expectancy, which is a trailing indicator.

It's the most recent data available. The fact that a lot of the data about the medical system is 20+ years old is in fact one of the biggest problems.

Also, I'm not in any way dismissing the contributions of modern medicine. As you say, modern medicine has contributed an enormous amount to society. Which makes it all the more unfortunate that many of its most vocal supporters wildly exaggerate its benefits and stick their heads in the sand when confronted with its problems. Making an intellectually honest argument in favor of modern medicine has to be one of the easiest tasks in the world, so the fact that so many of its supporters can't even do this doesn't say much for the quality of their ideas.

> Trying to prove that modern medicine has a net negative value because of a few issues of systemic corruption is not the way to do it.

I'm not trying to prove that it has net negative value. However, it's definitely not just a 'few' issues with systemic corruption.


It doesn't have to be features that are required. Another OS version just requires more development time and more testing resources. There are lots of little things that you discover break if you develop on the latest OS, and then test on the older one (or vice versa; neither forwards nor backwards compatibility are perfect). At this point, 10.8 is out, so developing on 10.5 means you need to test on 4 different versions, each with their own quirks, just for Mac OS X.

Obviously there are no features that are required to display a web page that are missing on 10.5. Browsers were developed and ran perfectly fine on there. Some newer features might not work, or some newer optimizations. But remember, keeping around all the old code paths, that check for particular features, can lead to more development cost, more testing cost, more bugs, more security vulnerabilities.

Another example is security features. Snow Leopard (10.6) introduced some new security features, like stack protection and more sandboxing. Chrome is heavily focused on security, and they may not be able to provide the full isolation that they would like on 10.5.

I develop software that should by all rights work fine on 10.5. And nothing that we do can't be made to worth there. But it takes more work; I develop on 10.7, we test heavily on 10.6 and 10.8, and when we go to test on 10.5, we find things that are broken not because they're impossible, but just because some interface is different so we need to add a new code path to handle that case. All that extra testing and development is expensive, and there are increasingly few people still on 10.5, so the benefit is continually shrinking.


Right, but this is Apple's own product. They had to be already set up for testing on 10.5, and made a conscious decision to stop.


Wait, what? Chrome is not Apple's product. It's Google's.

And being already set up for testing does not make it free. Hardware dies, and you have to replace it. More and more developers move on to newer OSs, and it becomes harder for them to get all of their development environment working in the older OS to find and fix bugs.

Have you ever tried developing a product with backwards compatibility across 4 different OS releases? It is by no means easy, it limits what you can do, and it makes your software more complicated and bug prone.

Don't think of it as having to make a conscious decision to stop. It's more that you have to make a conscious effort, that gets greater as time goes on, to continue supporting the older release. More libraries that you use start dropping compatibility. More new features have to be ifdef'd out, leading to divergence in what your software supports on different systems. More effort has to be put into keeping the build system running. And more manual testing needs to be done.


What, exactly, is Apple to test? They're not shipping updates to 10.5, and Chrome is Google's product to test.


He explained it all in his comment.

(1) Being "already set up for testing" for an older OS version

and

(2) continuing to use the testing setup for that version in addition to ever increasing new test setups (for 10.6, 10.7. 10.8 etc) and codepaths

is not the same thing.

As you get newer OSs to support, maintaining older testing setups means more work, and more IFDEFS and such in the code.


I am not too bothered about them needing to do more work given that they produce a premium product, in fact putting more care in is their entire shtick! Car makers don't stop making spare parts a couple of years after a new model comes out. If they did no one would buy them.


>I am not too bothered about them needing to do more work given that they produce a premium product, in fact putting more care in is their entire shtick!

Putting more care in the LATEST offering. Putting more care in older versions if a loosing proposition.

And it's not just a "throw more people / money at it" problem. After some point the complexity of legacy support grows exponentially and the code suffers (or gets hold back).

>Car makers don't stop making spare parts a couple of years after a new model comes out. If they did no one would buy them.

5 years in computing is like 20 car years...


> You can only put up products that exist.

That's not true. You can demonstrate prototypes. What you can't do is just whip something up in Blender, do a nice rendering, and then start selling it with with the rewards being "1 widget, 2 widgets, 5 widgets, 10 widgets, 20 widgets", with no indication that you've actually done your homework to say if this is even possible.

They want people to actually have some sort of prototype, something to show for their work, rather than just a slick graphical presentation and reward system that implies that it's far closer to completion than it actually is.


For one, when travelling, you can sometimes go for a while without having a chance to plug in and charge (due to not being on one place for long, bags being inaccessible, not having outlets on a long plane ride, etc).

But even when not travelling, I will sometimes forget to plug my phone in one night. It's really frustrating when it dies the next morning before I have a chance to recharge it again.


I've always wondered; how many pieces of much value can be made from lumpy, soft plastic with a low melting point? The results I've seen always look lumpy due to the resolution of the printer, the plastic isn't that hard, and the melting point is pretty low.

While I've seen a few neat things of novelty value, most of the actual things that I would want to make would require metal or harder plastics, and a lot more precision than these things are capable of.


I have an original replicator. With a little practice, you can have much nicer results than the 'lumpy prints' that you describe. Also, ABS is really easily sanded and is quite solid if you want professional looking parts


I'm curious what actually useful parts you've made from it. I'm not sure I have ever had a problem where the solution was a part that I could print on a 3D printer; but maybe I'm not being imaginative enough, so I'm curious what other people have done with it.


At places like shapeways, they have the big printers. Those can print some sort of metal. I have a sample, it is rock solid.


"No wireless. Less space than a nomad. Lame."

I'm not a big supporter of Windows 8, but writing them off based merely on price and specs seems a bit shortsighted.


This was an attack article through and through.

The author chides them for not using a more powerful processor (that would kill the battery life), when Microsoft worked directly with Intel and had them build a processor designed specifically for the Windows 8 kernel that would offer the longest possible battery life.

Shortsighted indeed.


Difference being iPod 1 had a much, much better UX than a Nomad.

Anything with less than 200DPI is not going to deliver that in 2012. Even at $300 it would be barely competitive, and at $600 it'll join the Xoom in forgotten tabletland.


Wasn't the first ipod, however huge it seems by modern standards, also substantially smaller than the nomad? My recollection is that the nomad was, well, a brick...


Most consumers neither understand nor care about the spec sheet. Reasons that make sense to an engineer are alien to most of the market.

They typical consumer asks for more gigahertz either as a status symbol or because something is slowing down their existing machine to the point that routine interactions are painful.


> based merely on price and specs

Beyond the price and capabilities, what else should the consumer consider?


Capabilities != specs.

But as an example, why not consider easy of use?


You're comparing the iPad with the Nomad? A curious analogy.

EDIT: I do know about the old Slashdot meme. I just think the situation is drastically different here, hence "A curious analogy".


It's an old slashdot reference. When the iPod was announced (the first one), that is what CmdrTaco said. CmdrTaco being the founder of slashdot.


It's a slashdot meme.

When the iPod was announced CmdrTaco said that, it stands as a classic example of tech geeks' tendency to focus on the details (specs, price, etc.) while missing the bigger picture. In that case superior design beats out a spec check sheet.

http://slashdot.org/story/01/10/23/1816257/apple-releases-ip...


Google that quote. It's from a comment on Slashdot a decade ago predicting the swift death of the iPod.


Did he ever claim it would die? http://slashdot.org/story/01/10/23/1816257/apple-releases-ip... just called it lame, which it was, not that people wouldn't buy it anyway.


Maybe swift death was an overstatement. He certainly wasn't a believer though.


What makes you unimpressed? Why do you think that Python clearly wins? Do you think that the additional type safety, namespace safety, and ease of concurrency in Go are worth nothing? Or do you just think that Python has more that outweigh that?

I know that I frequently kick myself in Python when I typo a name somewhere, and everything dies far beyond where I made the mistake because it goes along happily storing something into that typoed variable, and then when I read it later it has the wrong value, and it takes me a while to trace back and find where I made the typo.


This is what linting tools like pyflakes are for. Running it as a prerequisite to running the test suite means that I don't have to run all my tests just to find out that I misspelled a variable name.


Generally, I try not to use single letter variable names in any scope that doesn't fit into a single screen in my editor. That way, I don't need to remember what "f" means, it's right there in front of me. And I shouldn't have too many variables in that scope, so conflicts aren't all that important; if I really do, I just start using multi-letter names again.


This is a good heuristic. For me, single letter variables are almost always iterators in places where space is at a premium (i.e. one line list comprehensions in python). If I'm breaking a loop out over multiple lines (which is almost always the case), I prefer a longer, more informative variable name.


I'm not going to get into the politics of your post, but I will point out simple factual errors.

> Here in the US it used to be more subtle. Not now. Democrats openly channel benefits towards government and private unions as a way to buy their votes.

What "then" and "now" are you talking about? Democrats have been aligned with unions since at least FDR.

> If a being from another planet landed in the US and listened to Obama speak it would conclude that the only important people in this nation are "teachers, police, firemen and construction workers". Why? Because that is all he mentions in his speeches. Translated: "union, union, union, union".

I don't know why you think this is the case. Lets see, let's take an example from a speech directly to the audience most friendly to him; the DNC. And let's list all of the occupations that he mentions in a positive way:

1. soldier in Patton’s Army 2. work on a bomber assembly line 3. people in the shadow of a shuttered steel mill 4. teachers 5. students 6. scientists and engineers 7. small businesswoman 8. construction worker 9. workers ... who feared they’d never build another American car 10. business leaders 11. manufacturing jobs 12. jobs today building wind turbines 13. farmers 14. scientists (again) 15. construction workers (again) 16. teachers (again) 17. principals 18. students (again) 19. Americans who still serve in harm’s way

So, he mentions soldiers several time, scientists several times, businessmen/women several times, teachers several times, construction workers several times, students several times. He mentions farmers once, principals once, engineers once, and a few assorted manufacturing jobs (whether you count that as one item or not depends on how you categorize them). He mostly criticizes Wall Street and bankers. So, yes, he does mention the people you mention, but he mentions a bunch of other people as well.

> The last thing this country needs is more union workers earning $300K for life when they retire.

You are going to seriously have to stretch to find such unionized workers. Sure, you may be able to find one or two here or there to use for anecdotal evidence, but a few anecdotes do not make good evidence. Median wages for unionized workers are $917 per week (~$48,000 per year), median wages for non-union workers are $717 (~$37,000 per year). Source: http://www.bls.gov/news.release/union2.nr0.htm. And the premium for union membership is much higher for lower-wage jobs than higher wage. Source: http://lcc.aflcio.org/WhatsNewDocuments/EFCA/LowWageWorkers....

Unionized workers are not, in general, fat cats making six figures without working. They are lower wage workers who happen to have gotten a somewhat better deal than they could have individually via collective bargaining.


1. soldier in Patton’s Army (government worker) 2. work on a bomber assembly line (government worker) 3. people in the shadow of a shuttered steel mill (unemployed) 4. teachers (government worker) 5. students (unemployed) 6. scientists and engineers (working on government grant) 7. small businesswoman (private non-union!) 8. construction worker (private union) 9. workers ... who feared they’d never build another American car (GM + Chrysler = government worker) 10. business leaders (private non-union!) 11. manufacturing jobs (private non-union!) 12. jobs today building wind turbines (solyndra = government worker) 13. farmers (farming subsidy = government worker) 14. scientists (government grant = government worker) 15. construction workers (private union) 16. teachers (government worker) 17. principals (government worker) 18. students (unemployed) 19. Americans who still serve in harm’s way (government worker)

See a trend there? Pretty much everybody on that list has their hand in the government's pocket. Don't get me wrong, the Republicans aren't better ... but at least they'll lie to me and tell me sweet things. I'd rather be lied to.


So, generally each application needs to be authorized separately. I should have to type my password to allow this application to access my passwords. If I can just click "allow" with no password, then so can anyone else trivially with Terminal access.

If I go into Keychain access, and ask to see a password, it prompts for my master password before showing it to me. This should too.


From KeyChain's point of view, this command-line utility, /usr/bin/security, is no different from other GUI applications like Mail.app and Safari.app that relies on KeyChain to supply remembered passwords. If you expect KeyChain to prompt you for your master password when /usr/bin/security asks KeyChain for passwords, then you will be prompted every time Mail.app checks your email.

Actually you can configure KeyChain to do just that: just set the keychain to lock after 0 minutes of inactivity. But there is always the tradeoff between security and convenience. And when you give away physical access and a logged-in session away to a malicious user, offering protection will require a lot of inconvenience.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: