github.com/pkg/errors is a simple way to dump expensive stacktraces into each new/wrapped error. Or you can just panic and recover in your own app, it's possible though discouraged.
73 karma · joined February 21, 2011
github.com/pkg/errors is a simple way to dump expensive stacktraces into each new/wrapped error. Or you can just panic and recover in your own app, it's possible though discouraged.
How large was this whiteboard?
And then there's Venus' atmospheric pressure :-)
I am using LZ4 currently for a project compressing Netflow-derived data for a major ISP, even then it's in 64Kb chunks for quick access and decompression.
An argument could be made that [1986] would be more accurate.
The title of his article is "How the Asians became white" which as Eugene pointed out in the comments, is an allusion to "How the Irish Became White," by Noel Ignatiev.
So it wouldn't shock him at all, that's his point.
So, just speculating, he's no stranger to bandwidth spikes so perhaps the approach employed significantly saves on bandwidth during these periods, ultimately whether it's a conscious attempt to save or just a webdev quirk I don't know.
I've not found any such limitations with LevelDB
Prince Frederik for Australians.
Research the people, not the techno babble. If they don't submit to independent scientific scrutiny and approach ignorant investors individually, well there you go.
Just, wow. How does one even reply to a comment so profoundly stupid?
There's a wikipedia entry in combining standard deviations (Standard_deviation#Combining_standard_deviations) but it's dense if you don't have a math background (I don't have one). The crux of it is, to compute the stddev of a set you need to compute the average, then sum of squares of the delta [ie sum([elem[i] - avg] for 1 .. i)]. You don't have the individual elements any more so you can't compute the sum of squares of mean_deltas, but using the stored stddevs, means and averages you can recompute that information out when computing the new stddev.
Well, it's a lot of easier to explain with a whiteboard. You're basically subtracting out the information you don't have based on the stddev/mean-aka-avg/nelems data you do have, you're subtracting out infinite series and it all works out perfectly.
numsum1 = SUM(nelems[i] * (stddev[i]^2 + mean[i]^2))
numsum2 = SUM( nelems[i] * mean[i] )^2 / SUM(nelems[i])
combined_stddev = SQRT((numsum1 - numsum2) / SUM(nelems[i]))
Please don't do this.
I would read a book or 10 full of these old-school game developing anecdotes.