From: Stefan Lang <perfectly.normal.hacker@...>
Date: 2008-11-16T21:39:52+09:00
Subject: Re: web framework for Ruby 1.9

2008/11/15 Jeremy Kemper <jeremy@bitsweat.net>:
> On Fri, Nov 14, 2008 at 3:42 PM, Stefan Lang
> <perfectly.normal.hacker@gmail.com> wrote:
>> I'm looking for a web framework that:
>>
>> 1) really works with Ruby 1.9
>>
>> 2) pure Ruby code (i.e. doesn't depend on C-extensions, Java libraries...)
>>
>> 3) has an active community
>>
>> bonus points:
>>
>> 4) doesn't follow the "let's extend core classes whenever possible" craze
>>
>> 5) good postgres support
>>
>> Does such a framework exist or am I asking for too much?
>
> Rails satisfies all 5 for me, but you may find Active Support adds too
> much for your taste.
>
>> Actually I would use Rails, the latest RC is advertised as Ruby 1.9
>> compatible but I've immediately hit a couple of errors and I
>> don't have the time ATM to fix compatibility errors in such a big
>> codebase and push the changes upstream. What's more, the pure
>> Ruby postgres driver doesn't work anymore.
>
> What'd you run into? The only outstanding compatibility issue I have
> is with the test/unit -> minitest change.

* Creating an app failed with an exception. Installing the test-unit
  gem fixed that.

* Booting the application failed because config/boot.rb depends
  on a Gem::RubyGemsVersion that is not defined in the RubyGems 1.3.1
  that comes with Ruby 1.9.1 (I've got a fairly recent build from the 1_9_1
  branch). I fixed that by constantly returning "1.3.1" from rubygems_version.

* Freezing rails failed with missing method in RubyGems. Didn't find
  a fix for that.

* Rails didn't use the postgres-pr driver I installed with "gem install".
  (And that wasn't a RubyGems issue, it didn't work with postgres-pr
  in vendor either). Neither ruby-postgres nor pg built with Ruby 1.9.

> Rails has been chasing 1.9 compatibility like a drowning man gulps for
> air. Luckily the recent feature freeze means we're close to having dry
> land underfoot.
>
> The latest postgres-pr works, btw. The earlier driver was missing the
> #transaction_status method.

Great, where can I get that version?

Stefan