deweerdt

The H2O build produces libh2o and libh2o-evloop. The latter doesn't depend on libuv.

This is the only claim that i've found saying that throttling (or disabling, for that matter) renegotiation would prevent the issue: https://twitter.com/Unreal_IRCd/status/778975019829489664

The advisory makes it sound like that would be the case, but it would have been great if that was explicitly stated.

http://www.chessgames.com/perl/chessplayer?pid=15866 has a list of notable games.

I bought the app, and I'm really happy with it, thanks!

I know it's a long shot, but some sort of shell integration would be awesome. My typical day is > 60% iTerm2. iTerm2 has shell integration: https://iterm2.com/shell_integration.html, and maybe that would be one way is something that Qbserve could be fetching info about what's going on in the terminal.

The newyorker ran an interesting piece along those lines: http://www.newyorker.com/magazine/2015/11/16/politics-and-th...

I think that gofmt is particularly innovative, in the sense that it acknowledges that formatting is integral part of the language.

In the sense that a programming language is not only made to be parsed by a computer, but also read back by a human.

> Other musical spammers simply upload the same song thousands of times with different titles that are purposely similar to major hits

Reminded me of: https://en.wikipedia.org/wiki/U2_(EP)

Yes, that's my understanding of the implementation as well. I was commenting on the fact that you might have two totally unrelated p1 and p2, where (hash(p1) % SIZE_OF_POOL) == (hash(p2) % SIZE_OF_POOL), that will end up sharing the same mutex.

some context: https://www.psychologytoday.com/blog/the-teenage-mind/201106...

> gcc seems to use a fixed size "pool" of mutexes attributed to a shared_ptr according to a hash of its pointee address, when dealing with atomic operations. In other words, no rocket-science for atomic shared pointers until now.

A side effect of the shared pool is that you might have two totally unrelated pointers share the same mutex, leading to surprising locking behaviors. Something to keep in mind.

Note: this is from 2007 and discusses 32bits x86 disassembly.

MySpace had (has?) an MS stack, and it was called successful at one point.

I see warning as an error where some acceptable course of action could be taken without needing to abort the action.

For example, the user has provided a config with two TCP ports to listen to, but the program only supports one.

You can either error out, and abort the action to listen to a port, or warn the user saying that you chose one of the ports, and proceed with listening to a port.

> I'm kind of dissapointed that the rest of the world didn't pick logging to a circular memory buffer like varnish does. It's proven extremely useful. You'll have a full firehose of information when you need it without sacrificing performance

Aren't you incurring a cost for logging for stuff that would end up being thrown out?

cloudmark.com - System Software Developer - San Francisco, CA - On Site - Must be eligible to work in the US We're a small team developing a high availability, high performance messaging (SMTP, SMS, DNS) gateway on Linux. Our software is mostly developed in C and uses python for automated testing coverage. We're looking for someone passionate about technology, who has an eye for performance and has some familiarity with Linux system and networking and C.

Email me at fdeweerdt[at]cloudmark.com

From the paper: "YouTube is consistently more permissive in the counts for monetized views, when compared to the public view counters. Specifically, fake views are penalized and not counted by the public view counter, but are monetized, i.e., have paid-for ads delivered in them, and counted in the the video owner’s monetized views."