skysight-inc/HackerNews huggingface dataset:
If you think big banks should be the world's money police, then yes.

Honestly, I would rather have that than have the federal government do it with a giant NSA-for-banks program. But my inner libertarian finds this arrangement suboptimal. And the government is probably watching it anyway. They certainly have an enormous amount of subpoena power, to the extent that big finance companies have IT systems just for satisfying subpoenas and ever-increasing regulatory data requirements.

Edit: the answer to your question, supposing it's not rhetorical, is "yes". Elites and their subordinates have the same ethical incentives as everyone else, but are closer to the political source. This can be good or bad. I think a lot of history happens because of elites realigning their moral goals in response to incentives.
Lessons and Surprises from an Agile Process
Isn't this done client side? Without joins in the db engine itself locality is much worse along with lost opportunities for optimization leading to much worse performance.
Many people already build data warehouses for analytics purposes, you don't want to be running reports against your live datatbase if you don't have to. Why add extra load?
Vuo in Beta: A New Hope for Visual Development?
Show HN: We built a video game for Node Knockout 2013
Unencrypted basic auth as a means to authenticate REST API access is a bad idea. Acquire an SSL certificate.
This is pretty awesome. And it is the first time I've heard of someone doing this with precipitate chemistry which seems really clever.

It also brings a lot of questions to the table which, when answered, will push electronics prototyping to a new place.

First is signal integrity issues. Getting some electrons from point A to point B is cool, getting them there along a path that consistently has the same impedence is a bit harder, do able though with sufficient control.

It's fortunate that many of the inkjet patents have expired, that kept this approach pinned up for years. I look forward to these guys getting funded and moving the prototype PCB market from a pint of etchant and a copper plated board, into something more advanced.
I was the author. Now I'm a guy who wonders if those are my memories, or Tyrell's niece's memories ;-)
This image describe my feelings:

http://developer.rackspace.com/images/2013-11-11-peanut-butt...

Why not just come up with a sane deployment strategy instead of hacking LXC to do it?

While Docker is interesting, we've been doing the same thing with OpenVZ for years now, minus a lot of the hype. Containerization is great but it's being applied to the wrong problem.

As a Linux admin, the claim that it's 'Portable' really irks me. Portable, in this context, is misleading, as it normally implies your application can run on different CPU Architectures. Apple's Universal Binaries were portable. Docker is not portable. It doesn't even support a large number of Linux distros. Good luck running it on FreeBSD or OS X without a lot of headache.

Docker relies on AuFS instead of a more modern COW filesystem like ZFS or btrfs.

Troubleshooting this in production will be a pain (no way to meter IOPS, no support for IPv6, unsupported filesystem, huge security risks over real virtualization).
> Seven-table joins. Ugh.

What? That's what relationship databases are for. And seven is nothing. Properly indexed, that's probably super-super-fast.

This is the equivalent of a C programmer saying "dereferencing a pointer, ugh". Or a PHP programmer saying "associative arrays, ugh".

I think this attitude comes from a similar place as JavaScript-hate. A lot of people have to write JavaScript, but aren't good at JavaScript, so they don't take time to learn the language, and then when it doesn't do what they expect or fit their preconceived notions, they blame it for being a crappy language, when it's really just their own lack of investment.

Likewise, I'm amazed at people who hate relational databases or joins, because they never bothered to learn SQL and how indexes work and how joins work, discover that their badly-written query is slow and CPU-hogging, and then blame relational databases, when it's really just their own lack of experience.

Joins are good, people. They're the whole point of relational databases. But they're like pointers -- very powerful, but you need to use them properly.

(Their only negative is that they don't scale beyond a single database server, but given database server capabilities these days, you'll be very lucky to ever run into this limitation, for most products.)
Hm, I assume you reached out to the mailing list and what not? I know a number of installations with numbers well above that. Were you using the batch insertion API?
Google autocomplete poetry
I have a production app that generates about 500MB of data per day. A small amount of that data needs to be kept hot in cache -- but the rest is accessed infrequently by comparison (but still in a manner that is aided by SQL). No problems at all -- system runs smooth as silk.

The problem is the application was developed based on the specs advertised (as I'm sure countless others also were). Now, the smallest database package with the same storage and connection resources is the "Standard Baku" at $2,000/month. These resources used to be available starting at $50/month. Ouch!! And even then, it is still only the "Standard" feature set -- so none of the new whiz-bang Heroku 2.0 features.
I know the performance servers improve it, but I'm specifically asking about the standard flavors. On your competitor's system for comparison (standard image, smallest flavor, no bonus payments):

$ time nova boot ....
0.24s user 0.04s system 1% cpu 20.724 total
$ nova console-log
Cloud-init v. 0.7.3 finished at Mon, 11 Nov 2013 19:08:50 +0000. Datasource DataSourceEc2. Up 54.42 seconds

In practice that means <1min until the machine is ssh-able.

Smallest non-performance instance in rackspace ORD: around 5 minutes until ACTIVE.
... The fact that the display is minimalist is what makes it strong. It is not "another doodle". It is a quiet little red flower on a white background.

Personally, I would be more offended by a huge animation. Google is obliviously not trying to get some fame here. Instead of cashing on Remembrance Day, they put the flower on their homepage with a lot of dignity.
Gospel Singer Poses Naked
GOSPEL ARTIST POSES NUDE!

Evon Latrail is the author of a children's book "When Mommy Went to Heaven". She wrote/recorded a few songs; "Lord Bless My Enemies" and "It Is Time" happens to be two of the titles. She even has a song entitled, "Can't You See (Abortion Is Murder). She went Pro-life after having a abortion! Really???? Now here is a photo of her posing in chocolate as a "Swamp Girl". The word Hypocrite is floating around somewhere. This story has made front page news in the local paper. How can this so called "Gospel Artist" be a role model if she's posing news? For more on this story.....Go to Google or YouTube and search, Evon Latrail. I seen the picture on Google. Not to mention the video with her and a A list actor floating around.......
Introducing the Humble Store
I could probably whack something together, but what specifically were you wondering about?
US colloquial usage - where the original, subtle UK usage goes to die; see also "presently," and "beg the question."
Yes, that is in progress.
> Health is inherently social

Maybe wellness is inherently social. I am a huge fan of Strava.

But there is no way I would give three guys in Oakland access to my medical records.
How operations, design, and data affect software and business: Ops edition
Been working from home full time for over six years now.

A couple of warnings:

1. A danger of working from home is that work is always just a few steps away. I've lost many hours of my social and family life because I had a thought running through my brain about a problem I was working on and just sat down for "a minute" to look at it. :)

2. If you work for a US company as an employee, the IRS tax credits for home office expenses are extremely unfavorable. Anything you want to count toward work has to be kept completely separate from home. If you store household junk in your office, an auditor can make the case the office isn't deductible. If you have a business internet connection, but it is also used in the rest of the house, you can't deduct the whole thing, only a fraction. When I tried to deduct the expense of building out my home office, it didn't work out to any sort of noticeable impact on my taxes. :/

Advice:

* Have a schedule and let people know when you are breaking away from it.

* Ensure friends and family know that when you are "at work", they should treat it just the same as if you were out of the house at an office. Make sure they don't feel it is acceptable to just come into your office and interrupt and that you might not be able to just take off on a whim.

* Have a pull mechanism for notifying co-workers of your schedule. People can get irked about lots of e-mails that you are going out for an extended lunch, etc. So set up a calendar or website where people can visit to see if you are available. Using the "Away/Busy" functionality of your IM client helps too.

* Have a pull mechanism for notifying co-workers of your work progress. Make sure you keep your issue management system up to date with what you are working on and lots of checkpoints along the way. A weekly status page similar to a blog might also help. Basically, provide your co-workers with an easy way to see where you are and what you are working on whenever they might need to without being barraged with e-mails.
Grammatical errors in a site's hero carousel make me wonder how much QA went into the product.
The more complicated I/we make/made this discussion, the more obvious it seems to me that having programmers who talk to each other is simpler than trying to make up and/or enforce rules to obviate the need for talking to one another.
Doctor performs surgery using Google Glass [video]
"Desktop-class"
Yeah, FlockDB (https://github.com/twitter/flockdb) comes to mind. I think Titan (https://github.com/thinkaurelius/titan) should / will be able to handle this too.
Holy crap. This guy still has/had a job?
Welcome to Texas! The winter will be a lot more fun than the summer was.
FWIW, I just talked to the author (Robert Graham) about it, and he responded:

"bah, I need to fix that"

https://twitter.com/ErrataRob/status/399979105854058497

EDIT: And he pushed a LICENSE file just now.

"I provide this code with no warrantee whatsoever. But hey, if you want to take the risk and run it, go for it."
you always could, see __import__ and imp module.
Open SBC runs Linux & Android on Allwinner A20
how about 3, err 13 people I actually care about?
> When you see code that hurts your eyes, don't just fix it; discuss it.

This.
Sure, I can see a few ways of this happening:

1) A virus provides some additional benefit. For example, if a virus' first stage acts as a sort of installer and pulls in some additional libraries for use, at some point of public infection rate there's a pretty good chance those libraries are available to anyone targeting programming for those systems. This becomes more feasible if AV cleaned the infectious and malicious portion while leaving libraries. Imagine, every system has libpcap one it...

2) Viruses start opening previously locked down portions of the OS to achieve their goals, and developers start taking advantage of these opening to extract more value for what they provide (in fact, being somewhat malicious themselves). This is already the case to some small degree with browser exploits. Keygen utilities that install malware seem to fit this somewhat.

This all presupposes a much more computer integrated and yet less computer aware society, which is where I think we are heading. More and more items have integrated computers and operating systems, yet we are much less aware of when this is the case (of course certain groups, such HN regulars, are more likely to be a aware of these items).

Edit: Here's a sample scenario for you: You turn on your new computer and attempt to use it to watch videos on your favorite site, but it doesn't work. You try again tomorrow and it does. What happened is that between then and now, a virus has infected your system and installed a hacked divx codec and made some changes in your browser to redirect you to some specific sites often. The author gets information about your system far beyond what is normally allowed, and you get access to videos as you normally did (possibly illegally).
I can't say how this specific CMU course compares with Ng's online course, but I can comment on Ng's course as compared to several other similar courses I took in Nanyang Tech. U. and Paul Sabatier (Toulouse 3), and my overall remark is that Ng's course is quite short on the maths, which makes it not sufficiently formal to deeply understand what goes on. However, it gives enough material and code samples to play with data. It can be nicely complemented with some self-study.
There are (perhaps literally) hundreds of reasons to not use godaddy. But why exactly aren't they trustworthy?
Offline capable peer to peer replication was the main reason I chose CouchDB - we needed something that would realistically run on clients, even mobile devices. NoSQL we mainly chose because we needed schema-less data (the whole system relies on ad-hoc design updates). It's basically an information system IDE with rapid application development.
But why would you do that? (The only time I've ever used that is when benchmarking and you need a clean cache between runs). Otherwise the kernel will just empty it as needed when you run a program.
> I must have read a dozen (conservative estimate) articles now all called "Why you should never use MongoDB ever"

Strange statistical oddity if you ask me right? How many "don't use PostgreSQL" or "don't use Cassandra" or "don't use SQLite" have you seen? Not as many. It is just very odd isn't it...

So either everyone is crazy or maybe there is something to it. I lean towards the later here.

> 1. Oh my God it's not relational!
...
> 2. Oh my God it doesn't have transactions!

Maybe those, you forget about:

3. Claim "webscale" performance while having a database wide write lock.

4. Until 2 years ago shipped with unacknowledged writes as a default. Talk about craziness. A _data_base product shipping with unacknowledged send-and-pray protocol as a default option. Are you surprised people criticize MongoDB? Because I am not at all. Sorry but after that I cannot let them within 100 feet of my data. They are cool guys perhaps and maybe having beers with them would be fun, but trusting them with data? -- sorry, can't do.
Have you had any experience with another provider or are you a first timer?
You're missing the point. The purpose of this post was to illustrate how silly little differences in coding style cause lots of unnecessary work. The agnostic's version was the best in this illustration because they knew what the requirements were. You can easily adapt the ascetic's, the librarian's, and the purist's version into the "right" code as well.

The point is that we each have our own different style of doing things, and frankly, I'm a bit incensed that you're using this post to hold up your way of doing things as the "one true" way of doing things while calling everyone else a "poser". I think this comment is exactly what the author is trying to say is bad.
I think that's FOSS compatible.
Proposed London Airport Island design unveiled
Thanks Craig! I missed the legacy pricing page and edited my post to reflect this. To make this more clear and transparent, I would include a link to this directly on your blog post. It certainly would've helped me.

If you wouldn't mind me asking, why the removal of the Kappa/Fugu/Zilla price points in the new tiers?
I recently moved to the VC side from software engineering. I was sure that the biggest value that I'd have for startups would be my engineering experience, but what founders seem to appreciate most is direct feedback. Even when saying 'no', I try to add some useful bullet points about what my fund's concerns are, what we'd like to see in order to invest in a latter round, any oddities that I noticed on the website or mobile app, etc. Founders seem to really like that -- especially product feedback.
Though of course some people prefer the OOM-killer to kick in fast instead of the whole system being unresponsive for about an hour or so.

That's why my desktop and laptop systems don't have swap enabled.
We have Cloud Queues, DNS/cloud load balancers, and Akamai CDN built into our Cloud Files system. We don't have have an elasticache equivalent at the moment
My point is $8/mo feels like less than $250
The whole post hinges on the statement:

"When MongoDB is all you have, it’s a cache with no backing store behind it. It will become inconsistent. Not eventually consistent — just plain, flat-out inconsistent, for all time."

OK, here is a chance to share a little insight. At what point did Mongo become hopelessly inconsistent? Were you ever able to determine why? Why bother with cute pictures and verbose explanations of simple schemas when the conclusion is just that Mongo breaks no matter what without further explanation?
Typically as your data model complexity ("relatedness") increases, it's more difficult to scale. I'm not sure about anything like CAP, but I do know that in graph-database land we have to remind ourselves that general graph partitioning is NP-Hard, and that our solutions will need to be domain-specific.
When you start the container you can specify which port you want using the -p command.

This command would start it on port 8000, but you could change to any other port you want, assuming it is free.

$ docker run -d -p :8000 kencochrane/django-docker

I'm also pretty sure that when your host is restarted the container will start back up when docker does, if the container was running before the host was restarted.
Disclaimer: I'm currently doing my PhD in biometrics so i'm a bit biased.

Retinal scan is invasive, difficult to separate users, and just unnecessary given current tech to ever be used ever again. Face recognition is doing very well, and latent fingerprint is getting better than better, so using one or the other (IMHO) doesn't really matter at this point. What does bother me is that mcafee doesn't address larger issues:

- How are you preventing spoofing? What kind of live-ness tests are done? (I guess not wanting to reveal this could be security protocol and the absence of evidence is not the evidence of absence, but i'm assuming that more than the average person would come to the conclusion that a fingerprint or face can be spoofed)

- two-factor authentication is good, but 2 layer security is bad - if people have to use their fingerprint AND a pin, they'll get lazy and revert to one or the other. There are several papers on biometric key generation where a biometric is used to build a certificate-key authentication. Heck there are even papers where the key is embedded into the biometric template. Biometrics are already walking a fine line between privacy and security, an easy and positive experience will go a long way in continued use and development.

- scaring people that hackers are going to steal your fingerprint - templates do not need to be stored as a raw image/minutiae points/facial features/etc. I think this goes back to the certificate-key relationship - use biometrics to build these, storing a raw template doesn't make much sense unless it's on an NSA server behind TS/SCI walls.
So handy
I knew in theory one can use mmap and unsafe pointer in go.

One main different between C and go is this:

C can type cast any mmap pointer and de-reference it got the values (pointer, offset to other locations) extremely fast - < 0.01 micro-seconds (assuming page is swap in.) BTW, I do track C line code execute time nano-seconds resolution all the time. It is not difficult to do with RDTSC instruction. It gave you timing resolution in term of CPU clock cycles - 1 2GHz CPU clock cycle = 500 picoseconds, One can easily see the system paging and context switching info from those resolution.

In C code, that is only a few assembly instructions. In go (or other GC type language) that one operations is translate to multiple C functions calls. That's probably tens if not at lease hundred times different in pure CPU cycles.

When one has to do this hundreds of millions times, that usually makes huge different in overall execution time. I personally know a lot of test cases that means minutes to finished certain operations v.s. days (+GBs of RAM).
So what's a better way to do it?

You need a documented system. If you don't have a documented system then there will be an undocumented system which is the same problem with less documentation.
Both awesome libraries, but I think including lodash and jquery in the list of small modules is a bit of a joke. Both are big old fashioned utility belts.

This

https://github.com/lodash/lodash/blob/master/lodash.js

is hardly the ~200 LOC module being described.
The author is not criticizing or championing anything. He's just being descriptive. He attaches to his description a reference to the psychological theory that similar people have an innate need to preserve a degree of individuality. This applies to tribes, romantic partners, and software development teams.

While one may or may not agree with Freud, the article is at least food for thought. Presenting software conflicts in this way asks us to acknowledge our instinctual psychological motives and question our claims of objectivity, technical soundness and pure logic. This kind of in-fighting serves only the individual and not the team.

Personally, I think there is great value in having a plurality of ideas and voices, but in a commercial setting, they must ultimately serve the team. This creates tension because individuals must be able to restrain their impulses.
Joins are potentially explosive (cartesian explosion :). So they have to be treated with respect, just as other explosive substances should be. That doesn't mean they should never be used - modern industries use thousands of dangerous things routinely. But proper handling is necessary - indexes, watching the data consistency, etc. So it is a good instinct to feel uneasy when there are seven joins around. It's not necessary fatal but it is something that would require attention.
As it says in the post - the prices of the performance instances is lower than the standard flavors, and we will be phasing out the standard (Non Performance) flavors as we complete the rollout to all data centers.
You're eating apples wrong
That is unquestionably a concern. I think you overrate it, though. Having more diversity in working hours would often lower latency, as there's someone available during off-hours rather than having huge gaps. We're also already dealing with a certain amount of distribution with timezones in (sorry for the cliche) "our increasingly globalized world" - I don't see that spreading that around more is going to cause more problems than it solves. As pointed out elsewhere, spreading out peak usage of things like roads and electricity provides significant benefit.
If it is a thin layer around libguestfs, why would Python be slow?
If they bought out Foursquare... Oh my. Now there's an acquisition worth a billion.
I see what you mean. Saying CSS/HTML would be a more precise way of describing this.
I work in the healthcare space. This seems like a HIPAA nightmare, but I;m sure they've thought of this and I would be interested in their strategy for dealing with HIPAA.
This is correct. They are also not singling out Bitcoins either. It has been in the news recently with banks closing accounts of money transfer businesses [1] due to the risk of money laundering. Therefore if money transfer businesses dealing with "conventional" currency are too much of a risk it is no surprise they'd not allow a company dealing in Bitcoins to hold an account.

---

[1] http://www.theguardian.com/global-development/2013/jun/24/so...
NSA's Surveillance Powers Extend Far Beyond Counterterrorism