skysight-inc/HackerNews huggingface dataset:
Interview with GoCardless Founder Matt Robinson
Scala has a much more powerful type system than Clojure
There is a huge gap between Pandas and Hadoop. That gap is well served by a $2-3k Postgres box with 32-64GB ram and 5-10TB of disk.

The main reason to switch to Hadoop at the point when Pandas fails is because you expect to scale past that gap fairly quickly.
I fell victim to the snooze button for years. I'd set my alarm early, and then hit snooze for literally two hours every morning.

I finally started getting up early by ditching my alarm clock altogether. Once I did that, I just started getting up the first time I woke up each morning.

I think this approach works because you always wake up at the end of a sleep cycle. I haven't used an alarm clock in over 10 years, and I am way more productive because of that.
Our electronic devices: The minerals have bankrolled unspeakable violence
As somebody who attended this conference, and hadn't had much exposure to C++11 features outside of 'auto', my personal biggest takeaway from almost every talk was this: Stop passing your sink variables as const refs.

That is to say if you have a constructor:

MyClass::MyClass(const std::string& s) : m_s(s) {}

That you call like:

std::string s = "Some string";
MyClass c(s);

You're hamstringing the compiler into always copying that string instead of being able to use the new move semantics, because it can't mess with the guts of a const reference. Instead, do the previously unspeakable evil of passing by value and then moving, e.g.

MyClass::MyClass(std::string s) : m_s(std::move(s)) {}

This lets the compiler know that if string has a move constructor, and is an rvalue, it can just move the guts into place instead of performing the copy, since the variable is 'sunk' into the new location. Huge wins all around.
sorry i dont give much value, but: wow. i imagine it'd be great to have this for desktop, combined with wacom tablet.
Big advantage of Hadoop is that you do not need to pay license fees which in case of relational databases can reach into tens of thousands dollars.

The big disadvantage is that Hadoop is two orders of magnitude slower than relational databases. Also, Hadoop clusters are not what one would call a "green" solution. More like a terrible waste of computing resources.
A lot of epidemic diseases that plague us come from animal farming. Ever wondered why diseases have names like "chicken pox" or "pig flu"?

That effect might even have helped in conquering the Americas, because the conquerors where used to such diseases and the natives where not.
CMU Creates Practical Self-Driving Car
Do you still have to set the column widths explicitly? That was one of the main reasons I had to drop this lib, because we had dynamic data and I didn't want to deal with adding a bunch of JavaScript on top to resize columns on the fly when the data changed.
The comment did mention that a majority of people can take heroin and lead stable lives while enjoying that drug. It is, however, not reasonable or moral to simply ignore what happens to the ones who can't and are destroyed by it. I have met plenty of drug addicts, from all 3 cases. Those who can simply live with and without the drug, those who can as long as the supply is stable (this group, not the first, is the majority) and those who get destroyed by it in a matter of weeks no matter what.
Interesting, but it isn't really similar advice. Indeed, it sounds like absolutely terrible advice (unless there is some context that is missing).
Am I the First Teacher on Svbtle?
Manu Sporny on integrating Bitcoin into the web browsers
Well, I used Registro.br and GoDaddy a few times and think Registro.br is much, much easier. And, yes, you can register for more than a year.

Hosting on the other hand is terrible. Expensive and unreliable and with an awful customer service.
I think it is worth reviewing the "Schneier Doctrine" as I understand it:

Principles

* Security is a trade off between safety and freedom / cost

* Prevention is not always the most cost effective trade-off. Emergency response is often better.

* Stories make a huge difference in how humans perceive threats around us - and can therefore make a difference in correcting the perceived threat model to match the actual threat model.

Doctrine (not sure he has ever voiced these...)

* Define National Security quantatively (less than 1,000 expected deaths, or loss of less than 1% GDP its not national security). If someone slaps a National Security Letter on you today, its laughable, if personally threatening. If they slap a NSL on you when that means they seriously think a 1,000 people could die if you do not comply its not laughable.

* Massively increase spend on post-event support (ambulance, decontamination).

* Run public security "games" where teams of experts kill as many of us as possible using only items found in CostCo.
(Trying to reframe the perceived threat model to meet the actual threat model). Simon Cowell could present it.
Right. I got angry over the loss of time trying to figure out whether this was something I might be interested in or not. I don't take kindly to people wasting my time like that.
Looks like an amazing project. I think crowdsourcing is vastly underutilized for tasks like this.

May I make a suggestion re: the web site? In the home/registration page, it would be very helpful to link to some kind of description of the project, even if it's just one paragraph. Better yet, include that short description on the page itself.

As things stand now, I go to the sign-up page, but if I want to have any idea what the project involves before I sign up, I have to leave your site and go google the project (fortunately, there's an excellent Wikipedia article about the project).

Best of luck with your project and finding some good job candidates. If I were in a position to relocate, I'd apply for the job.
I don't know if 15/16 years of badly cured diseases with a pneumonia finale grande are really a solution here.

I don't even want to start with the side effects.

But yeah, funny ;)
I agree with the general thrust of this article. But hadoop isn't just for scaling up the absolute size of the data set. It is also useful for scaling up the absolute amount of CPU power you can throw at a problem. If I have 1 GB data set, but the computations that I need to do on that data set are complex enough that it would take a single machine a long time to do them, then hadoop is still useful. I gain tremendously by being able to fire up 100 extra large EC2 servers and run my computation much more quickly than I could with SQL or Python on a single machine.

Now some might counter this point with the observation others have made here that using hadoop imposes a ~10x slowdown. But even then, my 100 EC2 servers will get the job done 10x faster. Running a job in 1 hour with hadoop is MUCH better than running the same job in 10 hours without it, especially when you're doing data analysis and you need to iterate rapidly.

So there is a point where using hadoop is not productive. But that limit is not 5 TB and depends on a lot more variables. Over simplification makes for catchy blog posts, but is rarely the way to make good engineering decisions.
Perhaps.

But the problem is:

1980s: Their Evidence turns out to be a False Negative

2000s ("Oughts"): Our Evidence is Negative.

If they'd said "Our Evidence is Positive" it would be interesting. But it being Negative isn't so useful, is it another False Negative, or this time a True Negative?

Even today we know it was in part a False Negative, since Sadam himself thought he had some active programs; I don't think their Negative was of the "Sadam's spending the money but his underlings are pocketing it" type, which is not the sort of thing they or anyone not running a spy organization could have determined prior to the invasion and subsequent interrogations of the parties concerned.
Munich Starts Distributing Free Ubuntu CDs to Windows XP Users
I was with you until "and I can't recall anything like this for any other software."
We Watched the Ghosts of Google Street View Come to Life
Show first n paragraphs as a teaser
A class implementing IDisposable is that documentation. You shouldn't need more documentation than the fact that IDisposable is there.
Three Quick Wins for Responding to User Feedback
German Expert Warns Against Using iPhone5S Fingerprint Function
Nice to see DataTables on HN, thanks for creating a great library!

Just FYI, your library is being used clinically every day in a number of cancer centres in Canada as part of the open source QA tool for radiation therapy clinics that I wrote[1].

p.s. like others, I'm not a big fan of Hungarian Notation, but it's really no big deal at all and kind of a silly thing to complain about given how useful the library is.

[1] https://bitbucket.org/tohccmedphys/qatrackplus
On an unrelated note, what is the model of that keyboard?
One of the most important things is that enterprise drives are much more likely to be telling you the truth when they tell you your data is written to disk. Even if it hasn't actually hit the platter, they'll have a battery or cap backup power supply that allows them to write anything still pending to disk before they run out of power. Consumer drives often lie horribly about whether data is truly durable.
Web Firm EIC Sued by Pizza Place for Hijacking Domain Name
Show HN: Put the fun back into MailChimp autoresponders with MailPuppet
I'm always torn by these headlines: yes, many organizations lack the size of data required to take advantage of Hadoop. Few of the articles really bother explaining the advantages of Hadoop, and how what you're doing really moves the break-even point in terms of data size:

- 3x replication: if the data needs to be retained long-term, slapping it on one hard drive isn't going to cut it. This is pretty poor justification by itself, but it's nice to have.

- working set: if you only pull 1GB out of your data set for your computations, it makes sense to pull data from a database and run Python locally. If you need to run a batch job across your full, multi-TB data set every day then Hadoop starts looking more attractive

- data growth: a company may only have 10GB of data now, but how much do they expect to have in a year? It's important to forecast how much data you'll accumulate in the future. Especially if you want to throw all your logs/clickstreams/whatever into storage.

So, if you're expecting explosive growth, you want to hang on to every piece of data ever, or you're going to do a lot of computation across the whole dataset, it makes sense to adopt Hadoop even if your dataset isn't 'big' to start.

As for this article, the author undersells MapReduce a bit. Human-written MR jobs can jam a lot of work into those two operations (and a free sort, which is often useful). Using a tool like Crunch can turn really complicated jobs into one or two phases of MR. Once Tez is widely available people won't even write MR anymore, they'll all likely write a 'high-level' language and compile it down to Tez.
نتيجة تنسيق الثانوية الازهرية 2013
نتيجة تنسيق الثانوية الازهرية 2013 - http://www.alhqeqa.com/?p=22960
نتيجة,تنسيق,الثانوية,الازهرية,بنات,بنين - http://www.alhqeqa.com/?p=22960
نتيجة تنسيق الثانوية الازهرية 2013 - http://www.alhqeqa.com/?p=22960
نتيجة,تنسيق,الثانوية,الازهرية,بنات,بنين - http://www.alhqeqa.com/?p=22960
We are currently at the looking to move phase having come to the agreement that, yes, we are moving, and have informed our friends and family. What we haven't done is figured out where to go from here. Traveling seems to come up a lot in our family discussion, so we've agreed to do that for 6mo-1.5years. But after that it is the logistics of what to bring, what sell, what to store, and where to keep it.

We've begun to give/sell our things, throw out things when they're worn out or broken (we have a dining table with no chairs). Scan and shred the inordinate amount of paperwork a family accumulates over a decade.

Also at the end of our travels we're not sure where we want to be. Wife is EU passport holder and I am a US passport holder so either side of the pond won't be a problem as far as visas are concerned. But, those places are not where we want to live, yet. Places we're interested in moving to are AUS, NZ, and SA (costa rica, and chile for my wife). But we're not really sure we'd ever want to live there in the long term, either.

I'm curious if there is a short term visa that allows you to "sample" a country before making a big commitment. Most of the ones I've found appear to be for students under 30.
What I noticed in US is that people are very touchy about being uncomfortable. Doctors are supposed to "fix" problems and make things "comfortable". This usually means "give me antibiotics to kill this infections as fast as possible" and "give me more pain pills, I don't want to feel any slight discomfort". If doctor tells them to drink some hot tea and lay in bed instead they might just switch doctors who will give them antibiotics. Or say a doctor decides that well you can get opiates for your pain but you might become dependent so take some aspirin and tough it out -- that won't work with many.

I know I am painting with a broad brush and with a sample of 30 or so acquaintances from both sides of the "pond" here, but it was my impression so far.
Why wouldn't you give this value? I'm tired of drawing things on napkins and welcome this app.
That's totally understandable. Honestly, we haven't seen any appreciable difference in performance or failure rates between "enterprise" class drives and "consumer" drives (usually WD). Matching RPMs and cache sizes, there's just no way to justify the extra cost for them.

The one area we didn't penny-pinch on was the tape backup. Glacially slow compared to HDDs, obviously, but absolutely necessary.
There are also some things that are powerful but I'm not quite sure if I really like them. For instance, he promotes the use of handles instead of pointers. He goes through these variants:

Gadget* p = new Gadget(n); // not exception safe
shared_ptr<Gadget> p{new Gadget(n)}; //exception safe
unique_ptr<Gadget> p{new Gadget(n)}; //exception safe and less wasteful than shared_ptr if local
Gadget g{n}; //his preferred solution

My problem with his preferred solution is that I cannot know that Gadget is really a handle to a shared Gadget and not a big fat Gadget value on the stack. The only way of knowing that is to look at the implementation or the documentation.

So if g is returned from a function or passed to a function by value, I don't know whether or not a deep copy is made. If I manipulate that Gadget, am I manipulating a shared object affecting others or is this my private copy?

Qt uses that pattern throughout, and because it is used for everything in Qt, you know that you're dealing with handles. But the C++ standard library doesn't do it that way. Almost none of the classes in the standard library are handles.

If I see a pointer, shared or otherwise, I know I'm not dealing with a deep copy. I know someone somewhere else might point to the same object.
Postgres is free.
The landing page reminded me of this http://www.youtube.com/watch?v=yHiUitciuJ8
IPhone 5s: has Apple given up on innovation?
I read the list of comments and I find disappointing too see people saying things like "he talk simple stuff", or "this is too basic, I got nothing out of it"

I love those talks, and every once in a while I watch them again so I don't forget the basic principles.

Rich went 2 step ahead than simple state what some people feels as obvious: he created a language that implements them, and he communicated those concepts.

He did something to better the trade. Have you?

This is not about the next tool to make a quick buck, or cute, but impractical, philosophical concepts

And, I too would put "Simple made easy" as the first one. Then it becomes much easier to understand why functions are the 555 chip of software development.
Pirate Party Crashes Spy Drone in Front of German Chancellor Angela Merkel
MTTF should (and probably is) higher. Perhaps some other things like reallocated sectors count can be higher without affecting performance/stability much.

But from what I've seen, the most important thing is the service agreement, i.e. having new disk ready the next day without any questions asked (or money spent for a new drive).
I am not agreeing on this.
Unless you are hiring an expert, most of developers out there earning their lives by coding can not write a simple bubble sort when you give them a console.
Not because they don't have the capacity, They will either not remember the algorithm at the moment or haven't had a such situation requires similar approach at their previous work.
If you really want to know if he/she knows stuff, ask him a task/question/bug and let him explain how he would solve it. if he is good, he will start telling the approach in different aspects, he would even start writing you a pseudo code to solve it.

The approach taken in the article is not explaining how to HIRE programmers.

It is about how to ELEMINATE them.
> recommendations for entry level philosophy/ethics books

Nice (but opinionated and now ~50y old) overview: Bertrand Russell's "History of Western Philosophy". Long but extremely readable. Not necessarily very reliable.

Ethics specifically: Peter Singer's "Practical ethics". Note that Singer thinks that we (in the affluent West) should all be giving a lot more than most of us do to help less well-off people, and that non-human animals' welfare is much more important than most people treat it as, and he's quite persuasive. So reading his work might be bad for your financial and/or gastronomic well-being (but if so, you will consider that that's for the best).

Not all that entry-level but full of clever things and exceptionally clear (in approximately the way that maths/physics/computing people value clear thinking extra-highly): Gary Drescher's "Good and Real". Subtitle is "demystifying paradoxes from physics to ethics".

Just for fun: Quine's "Quiddities: an intermittently philosophical dictionary". Not really a dictionary, but a collection of short essays and remarks in alphabetical order of (single-word) subject. Quine was an absolutely first-rank philosopher, though he's not in particularly serious mode here.

Not at all entry-level (in terms of how hard you need to think; I don't think much expert philosophical knowledge is needed) but extraordinarily good and highly relevant to questions of ethics, though it's more about questions of personal identity: Derek Parfit's "Reasons and persons". He's more recently written a large two-volume work on ethics, which I haven't read.
Interesting, it looks like you made this for the iPhone and iPad and got very little love (no comments and only a few points) when posting as Show HNs.

What do you make of that?
> constructors should be as safe as they can be, which means no allocations, partial or not.

Can you expand upon what you mean by "safe" here?

If you mean "unable to fail", I vehemently disagree. Constructors should validate what is passed into them and fail if that is invalid. The alternative is to construct a zombie object that can't actually be used. Objects like this subvert the type system and lead to lots of unnecessary "if object.is_valid()" checks all over code that uses them.
Mozilla Webmaker: The web is still open. Hack it.
Obvious question: Any plan of porting this to iOS?

Or, Anyone know of an iOS app that does this?
I came here to make a joke about the real reason why was that no one understands them... but apparently everyone here does. Off to google monads for idiots...
Microsoft admits they were awful
Yeah, I agree that Brazil has a ton of brilliant minds and a very inventive people. But unfortunately, here in Brazil, ignorance is a bliss and a very profitable business.

Also, Brazil is the only country that treat treats his researchers like a fast food workers. Poor salaries (when gov. pay something) which obligates them in working on two or three part-time jobs, no gratitude (the phone card, the BINA system, which government didn't helped the inventor on recognizing the patent) and so on. That's why a researcher/cientist stays no more than 2 or 3 years in Brazil after graduation or research publishing.
I think it goes like this:

Certain very popular companies that everyone wants to emulate, who have truly enormous needs in the initial data crunching (e.g., ETL) department, were running into bottlenecks related to raw I/O bandwidth. They hit on a "let the mountain come to Mohammed" insight that helped them get past that problem, so that they could do their ETL jobs in less time and ultimately keep their workhorse databases (e.g., web search indexes) better-fed.

Simultaneously, a whole lot of people who were not having the same problems, but who want to believe that they are like companies who have those problems (because who doesn't want to be Google?) started also running into problems with handling large amounts of data. Unfortunately, the most popular mistake in applying Feynman's Algorithm[1] is to skip the first step. Rather than investigating their problems and recognizing that the issue was poor tooling or inefficient implementations and they weren't actually coming anywhere close to any true limits of the kind that the companies that came up with Big Data were trying to get around, they instead just went, "Hey, X company that we look up to is also having problems that look cosmetically similar to ours, and they use Y technology - let's give that a try!" and proceeded to dive straight into constructing bamboo control towers and coconut radios without ever looking back.

After that, well, I think it's a tragedy of mostly-rational behavior. Managers don't understand these technologies well enough to take programmers' advice skeptically, so they have to listen to their engineers. Engineers want to make their CV's look nice and impress their managers, so they've got every reason to come up with excuses to use $HOT_NEW_TOY. As usual, everyone individually acting in accordance with their rational self-interest is not the same thing as everyone collectively acting in a way that produces ideal results for the parties involved.

[1] http://c2.com/cgi/wiki?FeynmanAlgorithm
It's A Terrible Time To Buy An Expensive House
Oh sure. Actually that was part of my monitoring too (periodic reporting of outgoing natted connection).
Show HN: Readbox
This is my side project: a reader application with tons of feature (some of them coming in the near future). I would like to receive some feedbacks, note that the webapp is still in beta but we are making huge steps forward every day.

Please try it and share your opinion, thank you!

PS: The iOS client will be released in a month.
QuestionMark.js
Hard drives are tricky little beasts.

On the one hand, cheap disks are much more prone to start operating slowly when they begin to fail, instead of transitioning directly from working to not working (or setting themselves as failed).

On the other hand, RAID write speeds are roughly that of the slowest drive in the set. The more drives you have, the higher the probability of a malfunctioning hard drive making the whole thing go slow. Slow drives mean I/O bottlenecks, rendering the whole server unusable.

Pair both things and you have actually increased your effective downtime instead of decreasing it. Now use expensive disks (that work more reliably and either work or don't with a higher probability) and just calculate wether the price increase is lower than the cost of the downtime/slowdowns when running cheap disks.

Oftentimes the price premium is worth it.
Costa Concordia: Stricken ship set upright in Italy
I wouldn't doubt that either.

We do use RAID 6 (I think) + tape backups and the backup server itself is a hot standby. If you're curious, this is the chassis : http://www.supermicro.com/products/chassis/3U/836/SC836A-R12...

The motherboard is also Supermicro running dual AMD Opterons ( single processor on the backup server ) with 256Gb RAM.