We've used CommandChannel for about 6 years without issue ($0.18/slot/month), but for some reason certs need to be manually renewed. Pinged it with the Mumble client I'm building and got a cert that expired in 2012. something to keep in mind, I suppose.
This can be done very easily using an unbounded io.Reader instead of channels or iterators.
Here's a slightly modified version of bluefox's code where the prf function returns an unbounded io.Reader: https://play.golang.org/p/ZAj8q4eXEi
And here's a version that's modified a bit more, but still essentially the same, to trade LOC for matching the spec very cleanly: https://play.golang.org/p/Rpy0yIwVN1
Just to be clear, a Pipe counts as a channel for me; like I said, it requires a goroutine. Don't get me wrong, this is definitely the "right" go implementation, and what GHC does internally with thunks is way worse than goroutines.
The point is it no longer looks so superior to the Haskell version, especially since there were many LOC in the haskell version just defining the Key datatype which go never does.
I don't see any kind of error handling, but if I understand correctly, in some cases in Go it is not necessary to check for errors directly (an errorneous output stream would do-nothing on write, for example). Do you think your versions are fault-tolerant or is there anything you should add to gracefully handle errors?
Writing and Reading to a pipe only errors if the pipe has been closed. We return an io.Reader, instead of an io.ReadCloser, so consumers can't close the Read side. Internally, the Write side is never closed either. So, in practice, Reading and Writing also won't ever error.
The vocabulary of the grandparent comment implies they are using hadoop's streaming mode, and thus one can use a map-reduce streaming abstraction such as MRJob or just plain stdin/stdout; both will work locally and in cluster mode.
Or, if static typing is more agreeable to your development process, running hadoop in "single machine cluster" mode is relatively painless. The same goes for other distributed processing frameworks like Spark.
I haven't done any performance testing on large data sets yet, but in general I've been super happy with the Go's CSV library, both in terms of performance and ease-of-use.
If the speed ends up being a problem, it should be pretty easy to add a "--bail" flag or something.
From the article: 'The Department of Justice announced...that Cohen had presided over insider trading "on a scale without known precedent in the hedge-fund industry."'
"use the original title, unless it is misleading or linkbait."
The current title here "Inside the Biggest-Ever Hedge-Fund Scandal" is not the original content title (even if it is inside of the title tag in the HTML, as karkarlawawa noted) and is as linkbait as linkbait can be.
The HTML doc title is a legit option for "original title" and gets used all the time on HN. This title also isn't the worst linkbait we've seen (or even seen today). But you're right that it is hyperbolic and—uncharacteristically for the New Yorker—a bit breathy,
and also not something whose accuracy we're in position to verify, so we'll adopt your suggestion. Hopefully that will not lead to another big off-topic discussion the other way.
Well, it doesn't have to be a severe bottleneck in order for faster storage to be an advantage. If you've got two laptops with the same CPU and amount and speed of RAM, but one has a 30% faster SSD, then the latter will do a better job of keeping the CPU fully loaded.
yeah, it's a pretty hilarious game. Especially when combined with copious amounts of beer and the right kind of friends. I think this actually shows that there may be a big market for non-politically correct games and "stuff" that big burdened corporations won't touch, but the market would be more than willing to gobble up.
Daily deals like Groupon are fundamentally flawed in certain markets.
The problem is that it rarely generates repeat customers and/or customer loyalty - they tend to generate customers that come once, when they have a coupon, and never come again.
So unless your business is high margin, you're almost guaranteed to lose money from daily deals.
Thus, it's very good for things like paintball and skydiving and very bad for restaurants.
I think they mean that, out of their first 500,000 members, you were one of the first to register in Iceland. As in, you were one of the first people in Iceland to sign up for LinkedIn, and you did it very early.
"You were one of our first 500,000 members to register in Romania." He may be not out of their first 500 000 members and i think that applies to me too :). Something fishy with this message ... Result, no importance given or we both could call linkedin contact to see what's this about.
