Top

A Fresh Cup is Mike Gunderloy's software development weblog, covering Ruby on Rails and whatever else I find interesting in the universe of software. I'm a full-time Rails developer and contributor, available for long- or short-term consulting, with solid experience in working as part of a distributed team. If you'd like to hire me, drop me a line. I'm also the author of Rails Rescue Handbook and Rails Freelancing Handbook.


Navigation
« Double Shot #577 | Main | Double Shot #575 »
Wednesday
04Nov2009

Double Shot #576

DateWednesday, November 4, 2009 at 12:42AM
Today's challenge: Ziya Charts. If I'm not back tomorrow, I lost.

  • Mockingbird: New Cappucino-based wireframing tool. iPlotz and MockFlow are two other tools in this space (was just looking into this for a client yesterday).

  • First look at rails 3.0.pre - Dr. Nic dives into getting started and using generators.

  • Introducing Resque - The GitHub guys have built a new redis-backed background job library. Given some of the recent experiences I've had with their background jobs, I'm not all that sure the kinks are out yet.

  • Thinking_Sphinx - Easy Setup Tutorial - Quick start from Philip Ingram.
AuthorMike Gunderloy | Comment3 Comments |
in

Reader Comments (3)

What kinks do you think are present in Resque?

November 4, 2009 | Unregistered CommenterChris Wanstrath

Chris, I obviously don't know whether it's resque or something else, but I'm still seeing issues on what seems like GitHub's backend processing, including network pages that claim bounce back and forth between "there's more data, please refresh" and "please wait, we don't know" and a clone that took 12 hours and a support ticket to finish over the weekend. As a moderate user, my current perception is that GitHub is doing better now than before the server move, but there are still some things that lack the speed and reliability I'd like to see as a paying user. Good support and corporate transparency go a long way towards keeping me happy, but in the long run the underlying service needs to be fast and rock-solid as well.

November 4, 2009 | Unregistered CommenterMike Gunderloy

Got it, so it's a case of slow website = Rails can't scale, broken repo = broken job framework ;)

If you run into issues please repo them so we can investigate at http://support.github.com/dashboard

Cheers,

Chris

November 4, 2009 | Unregistered CommenterChris Wanstrath

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>