Comments on: No Callbacks, No Threads & Ruby 1.9 http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/ Internet Awesome Wed, 08 Feb 2012 06:24:37 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Itzy http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/#comment-6036 Itzy Wed, 26 Oct 2011 14:59:52 +0000 http://blog.envylabs.com/?p=748#comment-6036 Very interesting video! The new advantage will be great for us rubys Very interesting video! The new advantage will be great for us rubys

]]> By: MekEverve http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/#comment-2576 MekEverve Mon, 01 Aug 2011 17:39:29 +0000 http://blog.envylabs.com/?p=748#comment-2576 bb.txt open error bb.txt open error

]]> By: roger http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/#comment-2428 roger Wed, 23 Mar 2011 14:47:55 +0000 http://blog.envylabs.com/?p=748#comment-2428 I like fibers, but, as Ilya knows well, am not convinced they are the end all to rails scalability :) I like fibers, but, as Ilya knows well, am not convinced they are the end all to rails scalability :)

]]> By: Sigi http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/#comment-2047 Sigi Fri, 10 Sep 2010 14:49:57 +0000 http://blog.envylabs.com/?p=748#comment-2047 Thank you, Gregg, for producing this video, it's very well done indeed (as we've gotten used to from you by now ;-). It's a bit sad that the RailsConf organizers don't publish all of the talks like many other conferences do -- as if they wouldn't sell out the venue in that case... Thanks to Ilya, too, of course. This talk is very inspiring, probably the way to go for Ruby web stacks as he proposes. Thank you, Gregg, for producing this video, it’s very well done indeed (as we’ve gotten used to from you by now ;-). It’s a bit sad that the RailsConf organizers don’t publish all of the talks like many other conferences do — as if they wouldn’t sell out the venue in that case…

Thanks to Ilya, too, of course. This talk is very inspiring, probably the way to go for Ruby web stacks as he proposes.

]]> By: Jonas http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/#comment-2040 Jonas Thu, 09 Sep 2010 14:14:11 +0000 http://blog.envylabs.com/?p=748#comment-2040 While I am a newbie and did not get some of code examples at the very end, I really loved this presentation. Shows bottlenecks and how to "really" scale, banishing code now/scale later "fears" :) While I am a newbie and did not get some of code examples at the very end, I really loved this presentation. Shows bottlenecks and how to “really” scale, banishing code now/scale later “fears” :)

]]> By: Kristijan Sedlak http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/#comment-1973 Kristijan Sedlak Thu, 12 Aug 2010 13:30:40 +0000 http://blog.envylabs.com/?p=748#comment-1973 Waw! I like the idea! Waw! I like the idea!

]]> By: Delicious Bookmarks for July 27th from 16:18 to 16:44 « Lâmôlabs http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/#comment-1895 Delicious Bookmarks for July 27th from 16:18 to 16:44 « Lâmôlabs Tue, 27 Jul 2010 21:03:25 +0000 http://blog.envylabs.com/?p=748#comment-1895 [...] No Callbacks, No Threads & Ruby 1.9 « Envy Labs – July 27th %(postalicious-tags)( tags: ruby howto programming video async asynchronous eventmachine fibers )% [...] [...] No Callbacks, No Threads & Ruby 1.9 « Envy Labs – July 27th %(postalicious-tags)( tags: ruby howto programming video async asynchronous eventmachine fibers )% [...]

]]> By: Jose Cortinas http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/#comment-1881 Jose Cortinas Mon, 26 Jul 2010 22:55:53 +0000 http://blog.envylabs.com/?p=748#comment-1881 Ilya is the man. This same presentation was given by him at Railsconf 2010. Someone asked "What do you do when plugins or other software within your stack have memory leaks?" His answer was(pardon the langauge, just being accurate) "Simple, we fix the fucking leaks." Ilya is the man. This same presentation was given by him at Railsconf 2010. Someone asked “What do you do when plugins or other software within your stack have memory leaks?” His answer was(pardon the langauge, just being accurate) “Simple, we fix the fucking leaks.”

]]>