Most systems I know which require this just do at-least once on the sending side and dedupe on the receiving side. If you build this into your framework, to applications you have exactly-once barring unbounded partitions and the like.
This works only so long as the receiving side is able to retain all messages (or message ids if those are guaranteed to uniquely reference a given payload). It does not work for outages of unbounded (or otherwise impractical) data size or duration.
Not sure why this is being downvoted, it's actually a good question. If all of your VM's are idle, you would want your host CPU to idle as well, although my guess is this doesn't happen in things like Xen, VMWare, etc.
There has actually been problems with that, there was a bug with Citrix XenServer [0] where the CPU would, if left on idle for a long time, step down and turn off more or less all cores, which resulted in a locked up and unresponsive host. You can imagine what that did to the virtual machine supposedly running on that host.
"While an intolerant sect does not itself have title to complain of intolerance, its freedom should be restricted only when the tolerant sincerely and with reason believe that their own security and that of the institutions of liberty are in danger." - John Rawls.
Intolerance toward Prop 8 supporters is appropriate due to the threat to liberty that the restriction of same sex marriage creates.
There is no need to be tolerant of someone who threatens your security and liberty.
This was never about security or liberty (although it's a bit like the Monty Python sketch - "We're being oppressed, we're being oppressed! We really are!".)
I'm not saying there isn't discrimination against homosexuals in other areas, but this wasn't it.
This was basically a semantic debate about marriages versus civil unions.
A majority of Californians (Eich included) took the viewpoint that marriage was a traditional institution, and if people had a new style of relationship, they should have a new term for it, even if it had the same privileges (not rights - government's can't grant rights).
However, another group said no, we want to use the same word for it (I assume for ideological reasons, as opposed to purely utilitarian ones).
So no, please don't hoist the whole "WE'RE BEING OPPRESSED" flag - it doesn't help your case
That's incorrect. Prop 8 stripped all marriage rights. Most of those rights were restored by the time it got to the CA Supreme Court, but only because the CA Supremes said that Prop 8 was, legally, horseshit, but that to honor the will of the people they would let Prop 8 have the term "marriage". They're very clear about that in their decision.
The point of Prop 8 was to prevent gay marriage, and all the privileges that marriage includes. That is, to strip a civil right from gay people.
For thousands of years, we've had the concept of "marriage" and "families", and (more or less) monogamous relationships.
Central to this has been the idea of a man and a woman procreating, and raising children.
Now, perhaps we'll evolve away from that - maybe we'll simply clone people.
Or perhaps we'll have special breeder castes, and we'll raise the children away from their (biological) parents in learning centres.
Or perhaps the idea of having children will seem antiquated, and we'll just die away as a species.
Who knows.
But this (large scale homosexual relationships in society) is most definitely a new thing - and procreation, and nuclear families have no place in it.
Hence this whole ideological fight over whether to call it "marriage" (with all the associated ideas of families and raising children) or something else entirely.
Don't support welfare? You're against poor people.
Support welfare? You're against the working man.
You're pro-choice? You're against babies.
You're pro-life? You're against women.
Just wanted to say thank you for hlld/bloomd! At my old company we were looking into uses for them just because the idea and footprint was so cool. We had a couple ideas for hlld and the overhead was so small that we could basically add it to our servers for free.
> We figured pretty much everybody knows JavaScript
Even with the implied "everybody" being "everybody that would be interested in joining our site", this is a poor assumption. Not everyone is a ninja-rockstar web developer. In fact, some of the best content on HN comes from people who most likely don't know JS. I get the idea for the site, but the description seems very naive.
I know javascript too, and i've been contributing, but I don't know much about Node.js apps, Express, Mongoose, MongoDB or Jade, so my contributions have been pretty meager.
I'm still not entirely convinced that it serves as an adequate social filter, however, and I agree it might be too technically limiting to lead to a diverse userbase, but as an experiment I think it's worth watching.
Famous last words. I'm not saying that JavaScript is a particularly difficult language to learn, but most people make the mistake of looking at it's syntax and then concluding that "well, it seems pretty similar to Java, I can't just start coding away instead of learning about the basics".
What language would you recommend, if you wanted to make something accessible for, say, teenagers who haven't even taken the perfunctory "Introduction to Control Structures In Blub" course yet? Javascript seems like a good guess for "language you might pick up just from everyday computer use." (Another two being, I think, Windows batch files, and Excel macros.)
I can't imagine how anyone would pick up bits of js just from everyday computer use. How many people even now the the "view source" button in their browser even exists? Excel and batch files / shell scripts I could see though.
Consider you'll probably lose lawyers like Grellas and a few others who contribute a great deal here (I think rayiner, and people in other disciplines (a few scientists here and there) who may not know programming but know their vertical better than most hackers and have a lot to contribute in that respect.
It's an interesting idea for some kind of expertise test to contribute to a public forum, but it will be very self-selecting too.
You don't need to be a ninja-rockstar web developer to know js. But more importantly, I think it would be useful to emphasize the fact that pull requests don't necessarily need to be about improvements to code.
> People are like, ‘Andrew, what could be next?’ And it’s like, ‘Oh. Done.’ We have a mechanical bull. Game-changer. Innovate.
> “We don't call it an after-party. We call it after-hours.”
Waaaay too close to the Poe's Law line, I can't tell if this guy thinks this is for real or if he knows it's ridiculous and is just trying to cash in on demand.
What would be really cool is if this list of genres was open-sourced somewhere. I can see Netflix not wanting that, but it would really save time for however many hackers read this article and decide they want the same data.
A general thanks to aphyr for exploring all of these kinds of issues in distributed datastores at a level where someone without a lot of database knowledge can understand and reason through. If anyone hasn't read his Jepsen series and is interested in these kinds of things, it is well worth a read.
Of course, I wouldn't read it if you store very important data in any of the datastores he talks about, you might be scared to learn how your system actually operates =).
P.S. - The Spanner link is broken, you have some invisible character being added to the end, gets encoded to %E2%80%8E
