What kind of doctor would write such an irresponsible letter? Oh...
But the alternative is banning all information that anyone could possibly use to evaluate their own health.
stopped reading there.
339 karma · joined June 7, 2013
But the alternative is banning all information that anyone could possibly use to evaluate their own health.
stopped reading there.
>Quick, stop doing CT scans!!!???
Are you really this stupid? I think you're pretending to be stupid.
Yes, bad diagnosis is kind of a big deal. Yes, new, unlicensed, untested medical devices are kind of a big deal. Thanks for your completely unrelated, probably fictional, personal anecdotes though. I'm sure someone was swayed by your emotionally charged, whatever story about something whatever, but I'm surprised, because one time I got a rental car and it told me it was out of gas but it was wrong, I went to another dealership and there was gas! Quick, stop filling up cars at the pump!
Who upvotes this shit? Seems like there is a conspiracy to prevent legitimate and intelligent conversation around any medical issue by stupid, distracting comments and pointless bickering about issues that aren't even remotely related to the OP.
Considering the logical breadth and wiseness of the statement, I think the logical conclusion is to grant this engineer his own fleet of fracking equipment and a company to run it. Because then he'd make money and money is more money than no money. Everyone likes money but nobody likes a coconut to the head.
Drill on!
right, but it is the same at the same place, the database, so that's where you should put that constraint. There's not a lot of conceptual load here.
Put limits on the database so your database doesn't get knocked over. No, don't put limits in your client so your database doesn't get knocked over, put the limits for the database in the database.
I don't see where the gap is here. Sounds like premature optimization to me. Yes it does matter that Postgre abstracts the standard SQL datatypes away in the backend, no it doesn't matter what the performance impact of that is. Why? because unless you're committed to this database backend, trying to make it run faster is a waste of effort. Lets Postgre do that for you.
Do your job as a programmer and setup your database/schema right using the standardized standards at the standard level, then let the database do its job and setup the actual bits how it thinks is best.
Most people pay a lot more taxes because they don't have entire tax firms to leverage against their yearly tax return. Most people make a lot less money than politicians. Politicians often say that we need to pay for our public services in taxes. Politicians are often to take advantage of the social services of a society without contributing back with taxes, and people see that as taking advantage of the good will of people. Then when such people run for public office, people are disinterested to vote for someone who demonstrates no care for the social system that allowed them to employ workers and build a business.
This isn't a question of what people should do to garner public support. That's a red herring. Asking such a question is pointless. It's pretty much saying "well if I fed a poor person while I was ripping off hard working everyday people, would you vote for me then?"
Well.. no most people wouldn't, but it does tell us a lot about you when you ask that question.
As soon as it started getting features that would support this, the technical audience saw it coming a mile away and never adopted the required usage patterns needed to leverage such a monetization strategy. And not just because they wanted to avoid paying for music, but because the service model is just a pain in the ass compared to the self-service model.
"It could have been Pandora" ignores the fact that Pandora basically sucks and people just tolerate it. People want to be in control of their software despite what the business fucks running "IT" think now, conceptualizing a "service" where none is needed, trying to pull infinite profit from such trivial functions such as routing packets correctly or parsing compressed audio and routing it through hardware to a speaker without pointless and pathetic DRM algorithms trying to detect time-skewed copyright audio.. sigh. by setting the bar so low that people think that shitfuck-suck software is what you have to put up with unless you have "long term support" or other wedges into your conceptual/computational sovereignty to do something as simple as publish a document and expect it to be readable on another computer in 10 years, a problem that was solved 200 years ago is now the cutting edge of business technology and development, fueling well known multinationals such as Apple, Microsoft and Amazon.
Computing never was meant to be a platform for economic revolution, it just abstracts away paper work. You still have the exact same problems as with the internet as without it. I won't say the internet bubble is over until the world is actually simpler with computers instead of way, way more complicated and outright retarded in many aspects.
NO, WINAMP DIDN'T FAIL, in contrary, economic motivations failed to make Winamp suck, failed to steal a public resource and public work. Failed to co-opt the direction and passion of artists. AOL failed to capitalize on selfless engineering that actually solved a problem the correct way, it failed to corrupt the best solution with advertising indicators and economic feedback loops built into a market, shoehorned into an audio player. It failed to take us back instead of forward, like technology is supposed to.
I think the clearest indicator that WINAMP is a success, is the fact that XMMS exists, the fact that people use version 2.x without AOL's "support", 10+ years since release. It's a simple idea: a media player that supports plugins via a standardized API. (a real standard, not a "living standard" business-oxymoron) People still use it, for business and personal usage, and it doesn't tax them to do it, any more than a screwdriver taxes you, but not like the way a "service" taxes you.
I'm starting to wonder if this is really "Hacker News" or if it's "we want free advice and comments from engineers on our startups so lets start a forum with technical articles"
I never had any issues with Hadoop. Took about 2 days for me to familiarize myself with it and adhoc a script to do the staging and setup the local functions processing the data.
I really would like to understand what you consider "hard" about Hadoop or managing a cluster. It's pretty straight forward idea, architecture is dead simple, requiring no specialized hardware at any level. Anyone who is familiar with linux CLI and running a dyanamic website should be able to grok it easily, imho.
Then again, I come from the /. crowd, so YC isn't really my kind of people, generally.