dunk010

Absolutely dead wrong. It's 2.5Gb, where Gb = Gigabases. Learn you a genomics, son.

https://www.nature.com/nature/journal/v420/n6915/full/nature...

This is basically clickbait. Pretty much all the comments have the same sentiment: $425M is a lot of money.

Citation?

> There are valid reasons that long established companies such as Google, Twitter, Facebook and countless others chose MySQL as their primary data store.

I think you're misrepresenting things here. While all do use MySQL for some specific tasks, it's clear that all also have many other central datastores which are not MySQL. In Google's case this is a gross overstatement.

There's a good article from 2001 which explains this in depth: http://www.cdmasteringservices.com/dynamicrange.htm

Or IRC.

Landlord gets paid twice? Nice work if you can get it!

I'm sure this guy sneers at people who fall for Nigerian Prince emails, but he basically did the same thing. He allowed his own greed to cloud his judgement.

Actually there are armies of experts keeping this all up to date, and some companies make a lot of money selling this as a service. The name of the role is "curator", and they basically map research to genetic variants, keeping a giant library up-to-date.

Yes indeed. And new tools are being written - see the Adam project for an interesting example: https://github.com/bigdatagenomics/adam and the associated variant caller Avocado: https://github.com/bigdatagenomics/avocado. Others are also trying to get the old tools working on Hadoop, for instance Halvade: https://github.com/ddcap/halvade/wiki/Halvade-Manual, Hadoop-BAM https://github.com/HadoopGenomics/Hadoop-BAM, SeqPig: http://seqpig.sourceforge.net/, and the guys at BioBankCloud: https://github.com/biobankcloud. It's going to take quite a while for this stuff to get fleshed out, and for researchers to adopt it. But the sheer weight of data is going to force things in the Hadoop direction eventually. It is inevitable.

Paul Allen is well known to have one of the largest super-yachts in the world. I'm not sure Ballmer even has one.

I read this as "NSA data API" and it took me a full 5 seconds of staring, eyebrows raised, at the astronaut to realise my mistake.

By stopping reading Hacker News.

Thanks for sharing! Lots of great information in here. I've been a hiring manager for a role more than once and I can attest that it's all true. It would be nice if more people made CVs as easy to read as the tips here would produce. I even picked up one or two new ones for my own CV :-).

Hardly. There's a lot of great information in the presentation which is applicable to all developers.

Thanks for that. I had this strong feeling that this was very much basically the same as something (classic) that I had read before.

"that resulting shenanigans might be a little asymmetric. " - What does this statement even mean? You should think before you just throw a load of cliches into a sentence.

And if you know your phone is stolen you can disable it anyways.

That link doesn't work.

The streaming services don't make money either. In fact, Spotify makes a loss. A substantial loss. An eye-watering loss [1]. And so does anybody else who tries to get into this business. The trail is becoming littered with the corpses of plucky companies who've tried to make a buck in this business. Why is that? Quite simply, the music business is a cartel. It used to be the Big Six; now there's just three. Three companies who own the rights to most of the last half a century's worth of popular music. Here's the problem with Spotify's business model: they don't own what they're selling. The labels do. And so if Spotify makes a profit then the major labels can just renegotiate their contracts within a year (they typically have break clauses), and gobble up all those extra earnings.

You see the music business is a /nightmarish/ labyrinth of copyright legislation, so to even start playing in this game you need a staff lawyer (or three). There's recording rights, which you have to pay to one arm of the label. Then there's publishing rights, which you have to pay to a completely different arm of the label (or, if you're unlucky, a different label - like with the erstwhile EMI's catalogue), and that's just to play some radio. If you want to do on-demand streaming, of the type that Spotify provides, then you have to pay mechanical reproduction royalties. Whaaa? I hear you say. Well, it takes a while for the law to catch up with these things so they've just repurposed the laws that were already there. Would you believe, you even have a different bunch of people to pay if you want to reproduce the lyrics. Now, take all that and multiply it by the number of countries you want to stream in, because you're gonna need to strike deal with a different branch of each label in each country. It's insanity.

The one beacon of light is the much maligned DMCA act, which (aside for enabling content owners to persecute twelve year old children) allows those wanting to stream music in a radio-like fashion to just pay a central collections agency a fixed rate. That simplifies the business significantly - no more negotiation and complex contracts, and no more need to have such detailed reporting (less staff, less code). The only thing is that it's applicable only in the US, as there's no EU equivalent (or anywhere else, for that matter). And it doesn't cover on-demand streaming. But it's a start.

Music startups really need to push for an overhaul of the copyright laws because the landscape has fundamentally changed and what exists currently is both arcane and archaic. We need a complete legislative metamorphosis, lest the major labels continue to move their contractual blessing between startups - ideally, of course, shortly after a tasty IPO - which all resembles the classic pump-and-dump scam.

I hope it happens.

[1] http://techcrunch.com/2012/11/10/spotify-is-having-a-good-20...

Here's a really great presentation I found (probably on HN) some years ago. http://www.ukuug.org/events/linux2003/papers/bash_tips

All extremely useful, my favourite being the .inputrc rebindings of up and down to search history. Takes a little getting used to but is great once you are (good luck to anyone else trying to use your terminal though ;))

This is the best tip ever.

Very true. Options pool != stock the founders have. There are often many classes. It's never simple.

The auth.getMobileSession method in the 2.0 API, and the scrobble 1.0 API were both sticking points.

It's a 1 minute video so it probably took you longer to post this comment than to watch the thing.

Here's the thing: it's not real money. It was a part cash and part shares deal, and the facebook valuation is fantasy till they float. So what they were really arguing here is a) how much cash they could get out now and b) how much instagram is worth as a proportion of facebook.

One of my professors once related a quote from an author of one of the course texts. The author declared that you should "make my book the third book you read on this subject", because the third book you read on a subject is always the one that enlightens you on it :-). There are many paths to understanding, and I hope that the third book is still as relevant without the preceding two already digested.

True dat.

It weakens your security overall, as it provides another vector of attack.

You could just rip the trends information from Last.fm.