Tweetek
- Tweetek
- Tweets and replies
Celluloid and Celluloid::IO 0.16.0.pre2 released to RubyGems: https://groups.google.com/forum/#!topic/celluloid-ruby/3KqTEwYwv1A …
Celluloid has been downloaded over 3 million times: http://rubygems.org/gems/celluloid
Reel 0.5.0 released: https://groups.google.com/d/msg/celluloid-ruby/65JzG5jwPjk/orSAbssRBU4J …
Putting something cool into prod using @bascule 's @celluloidrb. So much fun working with actors
Thanks @celluloidrb, @bascule… you've doubled my performance, halved my memory usage, and saved me from callback hell!
@kennethkalmer will be chatting about @celluloidrb at the next Jozi.rb: http://www.meetup.com/joziruby/events/169952052/ …
Off to Manila tomorrow to speak about @celluloidrb and @jruby at @RubyConfPH. 

Shout out to @celluloidrb and @redisfeed, two of the best friends a job framework could have!
"Multi-threading with @celluloidrb"
This week's #crowdpost written by Gustavo Robles (@gus4no)
http://bit.ly/1g4WWxj
For our new app, @sidekiq+sidetiq is so much simpler & learner than the DJ/whenever setup we used 2 yrs ago. Wow! Thx @mperham @tobiassvn
We've just released nio4r 1.0.0: high-performance cross-platform asynchronous I/O API for Ruby: https://groups.google.com/forum/#!topic/celluloid-ruby/_q-Jg3C3PXk …
@celluloidrb @mperham don't forget Listen gem with more than 3 millions downloads! :) http://rubygems.org/gems/listen
Sidekiq, @mperham's job queue which is built on Celluloid, has broken 1 million downloads: https://rubygems.org/gems/sidekiq
Celluloid closes out 2013 by breaking 1.5 million downloads! Thanks everyone! https://rubygems.org/gems/celluloid
@artooio This code base is a good read! Haven’t used @celluloidrb yet but know a bit of Erlang. Nice example!
link: Ruby is alive and well | Seven steps - http://trevoke.net/blog/2013/11/11/ruby-is-alive-and-well/ …
We are moving the Celluloid BoF back to 8PM tonight so you all have time to eat dinner! Find us in Salon 2
We will be having a BoF session about Celluloid at @RubyConf tonight at 7PM. Join us!
Twitter may be over capacity or experiencing a momentary hiccup.
Visit Twitter Status for more information.