debuggergem to circumvent this issue. Or better yet, use
I've been working in a development environment that required an earlier verison of Ruby (1.8.7) that worked well with the ruby-debug gem. This gem is widly used and has some nice "get to know it" text in the rails guides.
In case you've been living under a rock for the past two years: Drupal 7 is known to use quite a bit of PHP memory everytime a page is loaded. I won't get into anything why that is and why it's such a big jump from Drupal 6 (I'm in no position to comment on that), but what you need to know is that Drupal 7 can easily use 40-50 MB per page load for a small to mid size website, and much much more for larger websites. Turn on some sort of PHP opcode cache like APC and you can probably get that small to mid site down to 10MB of usage or lower.
Last weekend @ DrupalCamp New Jersey, Tim Plunkett presented a wonderful alternative of the Calendar module for Drupal, called FullCalendar. I could be wrong, but I believe this was the first presentation given on the module which is very close to a stable release for Drupal 7.
At DrupalCamp NJ (the first ever, glad NJ is getting some love!), Jesse Beach from Acquia presented her thoughts how content is served in Drupal, and how to fix some problems that have surfaced over the years of web development. The traditional method for serving content to browsers is to have the server send off the entire DOM all at once.
I recently attended a PANMA event in Philly focusing on HTML5 & Adobe. Terry Ryan from Adobe gave a stellar presentation on a few things the company is doing to stay relevant in the rapidly changing web. It's no secret that Flash as we know it is dying off. A few months ago, Apple officially said they will not support it on iOS devices, and whatever you may think about that, the general consensus is that Flash will not be a player for much longer.