afhof

They just start sampling your data, the feature doesn't stop working.

When you buy premium, you get the unsampled data (and a person to call on the phone)

"(which it should already be)."

No, why should domains be required to attached to an individual person?

Dumping the entire database to disk on every write? I can't imagine more than 1 qps.

+1 to short and sweet incremental change lists. VLC / Firefox used to be this way until /someone/ deemed those not worthy. You can still get to the VLC changes which ware way more satisfying to read:

http://www.videolan.org/developers/vlc/NEWS

JUnit4 kind of helps with ExpectedExceptions. try-catch doesn't usually have a good reason to exist in unit tests.

libfaac is a safe aac default, but aacplus works MUCH better at the the 8 - 16 kbps range, which seams to be a stated goal of this page. It turns on SBR+PS and has ffmpeg support.

If any Dropbox people are reading this, can you comment on what criteria you used to pick the audio codec?

Are there ANY hardware manufactures that know how to write software? It seems like both firmware and hardware were an afterthought to almost any piece of computer hardware I have seen.

4096 is a good goal, but there is a much more obvious benefit at 1024 since it would fit within the IPv6 1280 MTU (i.e. a single packet). I recall hearing stories that the Google Homepage had to fit within 512 bytes for IPv4's 576 MTU.

Your mind fills in the gaps. What makes a picture NSFW is what it makes people think, not so much what it actually is.

The interesting effect of bubbling is not so much that people appear naked, but that the original picture, containing clothed people (typically bikinis), appear naked.

Is this even news? Pick any Wikipedia article at random that has more than one author. It isn't hard to find run on sentences and verb tense mismatches.

Does anyone seriously think that the difficulty with parallelizing code is the amount of boilerplate? The real problem is synchronizing multiple threads; being too lenient means deadlocks; being too strict means under utilization. The map() function doesn't really help with either of those.

In addition, it looks like you are unfairly picking on Java. The producer consumer model presented isn't anywhere near what a competent programmer would do. Building your consumer from within a method called Producer? Calling isinstance (or instanceof) to check if the "poison pill" is put in the queue? These are the signs of a crappy programmer, not a crappy language.

The language. Really the problem with SQL is the API. I like having a relational database, but SQL strings are a really crummy way of writing to it.

If you were to say "programming languages today are deficient in X, Myrddin fixes that!", what would X be? From the looks of it, it appears to be nothing. The syntax looks palatable and I like the lack of header files. That said, why would I be better off investing the time to learn your new language? (amongst the myriad other languages)

The "I'm doing this and I don't give a damn about you" attitude I think has at least some merit. If the lead programmer is good, its better if he/she can say no. If there is a correlation between being an asshole and being successful I haven't seen it.

Cox does something similar but bypasses the the DNS records and just slipstreams in a response. I noticed Cox would redirect javascript requests to their own HTTP server and put in their own snippets, effectively doing mass javascript injection.

The snippet ended up being some sort of alert about upcoming maintenance, but using a malicious technique for a benign purpose is the path to the dark side. Use HTTPS!

(I use 8.8.8.8, it didn't help)

100 and 120, at least in my brief experience. Coworkers start expecting 100% output from you, which means you are going to get a lesser review for putting out 80%. That they don't let you do 20% in the first 6 months there is what makes it so hard to start it back up.

I thought the segmented stack was the key to having hundreds of thousands of userland threads. It seems pretty farfetched (though not impossible) that realloc'ing the entire thread stack when it gets too big.

Its more link-baity this way. Instead of knowing what the article is about before clicking on it, you are now forced to waste an extra 10 seconds.

By the common understanding of alpha, pre alpha means its not really ready to demo.

Its deeply troublesome when these kinds of comments come up for two reasons: first and lesser: its wrong; secondly: its inconspicuously wrong. Processor speeds double approximately every generation which we can estimate is once every two years.

What do we have to count to: 2^128 = 3.402823669209385e+38

How many times can we count in a year with a 3GHz core: 3e9 * 3600 * 24 * 365.24 = 9.4670208e+16

In two years, when processing speeds have doubled? 9.4670208e+16 * 2 = 1.89340416e+17

How many years until a core can complete count to 2^128 in a year? log(3.4028e+38 / 9.467e+16) / log(2) * 2 = 143.21

So, in 143 years a single computer will be able to count to 2^128 in a single year. That's still a long time, but its WAY WAY less than the trillions of years people quote. Add in as many extra cores/machines/datacenters/planets of extra processors and you aren't really indefinitely secure. You are secure for a limited number of years and that's it.

"Beware of bugs in the above code; I have only proved it correct, not tried it."

It doesn't even stop at audio cable. Ever seen those "High quality HDMI cables? The bits on THOSE wires are purer than any other 1s and 0s. There is real money to be made in selling the emperor his clothes.

If you are summing up the whole experience rather than the audioformat, then you really don't have anything comparable. If one format really is better (and even that is subjective), then there needs to be a repeatable experiment that proves it.

Its painful sometimes to read audiophile forums. Often you'll see people claim that FLAC audio doesn't sound as good as raw PCM. Some people seem so proud of their ignorance that they ignore the benefits instead of trying to understand.

Its doubtful that the image can be recovered. The information really is gone. I suspect it would be easier to make it simple to have redundant copies of the data, rather than trying to fix the images after they're gone.

Nope, you should still validate your input. The correct thing to do is the validate that the input is semantically valid rather than syntactically valid. If they enter an address, try looking it up. If they enter an email, try sending a confirmation email. If they enter a phone number at least see if you can find it in a phone number DB.

Customers and users do have an interest in getting their shipping details correct. Help them get it right rather than telling them they're wrong.

You raise a point that I am not sure you meant to: Do people prefer participating in anonymous communities? Wanting to be anonymous and wanted to be with other anonymous people are pretty different things.

Nothing actionable in this post. If they said "OpenSSL is backdoored, don't use it!" then great. But, "Some software somewhere has a security hole in it", is pretty unhelpful.

The golden ratio method looks neat; but I think it can be forked into two algorithms. In the site version, they know ahead of time how many colors are needed. If you need n colors, you could use the multiplicative inverse mod n to pick angles along the color wheel. This results in every color being unique and as far away as the other colors as possible.

In the case you don't know how many colors you will need at the time of first picking you can use the golden ratio method to pick colors.