evadne

https://github.com/mperham/sidekiq/issues/2583 http://www.mikeperham.com/2015/10/14/optimizing-sidekiq/

Celluloid uses 1 thread per actor.

https://github.com/flyingsaucerproject/flyingsaucer

For more controlled results you could use Prince.

https://play.google.com/store/apps/details?id=com.brave.brow...

    $ curl -s "https://api.github.com/orgs/AndroidHardening/repos?per_page=200" | ruby -rubygems -e "require 'json'; JSON.load(STDIN.read).each { |repo| puts \"git clone #{repo['ssh_url']} android-hardening-#{repo['name'].gsub(/(.)([A-Z])/,'\1-\2').downcase.gsub(/[^a-zA-Z0-9]/, '-').gsub(/-(-+)/, '-')}\" }" | parallel -j 8 '{}'

https://github.com/holsee/chroxy

https://slides.com/holsee/deck-5

“Chameleon requires OS X 10.6 or higher. Apps built with it have been proven to be acceptable to Apple for the Mac App Store. Chameleon was first built by The Iconfactory to unify the codebase of Twitterrific for both Mac and iOS.”

Frameworks with iOS/macOS targets have long existed and it is proven possible to have events routed in UIKit style. I however fear that the merging of user experiences will come at the detriment of the Mac experience.

SJ said long ago that Macs are trucks and only some people need it. This converging step makes no sense when Apple is already trying to push the iPad as the “computer” for the masses.

Kushnick, B., $300 Billion Broadband Scandal [2009] http://www.teletruth.org/docs/broadbandscandalfree.pdf

[1] https://tfl.gov.uk/fares-and-payments/ways-to-pay/whats-the-...

https://blog.2ndquadrant.com/what-is-select-skip-locked-for-...

http://www.cybertec.at/skip-locked-one-of-my-favorite-9-5-fe...

Also, duplicate of: https://news.ycombinator.com/item?id=9576864

It is fine to have an engineer do both jobs, but my stance is that time spent on non-product engineering needs to be accounted under the proper accounting bucket, in order to avoid diffusion of responsibilities.

1. https://docs.npmjs.com/cli/shrinkwrap is a good thing. Please consider doing it for all of your projects using NPM.

2. Consider also putting your node_modules under version control.

https://www.postgresql.org/message-id/20151222124018.bee10b6...

“There's no substance to these claims. Chasing the links around we finally find this article: http://www.sqlskills.com/blogs/kimberly/guids-as-primary-key... which makes the reasonable argument that random primary keys can cause performance robbing fragmentation on clustered indexes.

But Postgres doesn't _have_ clustered indexes, so that article doesn't apply at all. The other authors appear to have missed this important point.

One could make the argument that the index itself becomming fragmented could cause some performance degredation, but I've yet to see any convincing evidence that index fragmentation produces any measurable performance issues (my own experiments have been inconclusive).”

My team has been using ScreenHero prior to Slack buying them out. ScreenHero also supports audio calls without screen-sharing, and its audio calls have not been problematic for us.