Ruby 1.8.3 has been released

But hold your horses on installing it for a production Rails system. At least one compatibility issue has been spotted between Rails 0.13.1 and Ruby 1.8.3. Over the next days, we’ll look for any other issues and be sure to resolve them shortly.

UPDATE: The Rails beta gems now include a fix for the incompatibility.

The wiki is down

While we’re working on bringing it back, you can get the HTML backup (2.6MB). The homepage for that export is broken, but the rest should be good.

Madeleine is so stretched beyond breaking point for handling a wiki the size of the Rails one. Ugh.

FCGI replacement in the making for Rails

Zed A. Shaw is working on a SCGI implementation in pure Ruby that’ll hopefully make for a more pleasant experience than FCGI once ready. He just announced the v0.3 of the SCGI Rails Runner and I’d encourage everyone to go have a look. It may not yet be ready to dethrone FCGI, but with enough exposure, it’ll hopefully soon be a viable alternative.

Ruby on Rails as a Burton Group telebriefing

The Burton Group advices Fortune 500 CTOs and other big shots on existing and upcoming technology. On September 28th, they will host a telebriefing using a panel discussion with Dave Thomas, David Geary, and yours truly. This briefing will come hot on the heels of a new report currently being prepared by the group that examines Ruby on Rails and encourage the enterprise to start getting interested.

The eight steps of a Rails conversion

Brett at San Antonio Safe List recalls the process that he has seen folks with PHP, Python, Java, and DBA experience go through when meeting Rails:

  1. Everything is so weird.
  2. Everyone is really annoyed by Rails’ “black magic” where all this stuff just happens for you.
  3. People realize that programming tasks are handled in a single line.
  4. They have to lookup how to do something Ruby.
  5. They realize how much faster they are building things.
  6. They forget about all other languages and stop saying “Well in Java I’d do this…In python it works like this…Thats just like the ternary operator in Perl…”
  7. They wonder why in the hell that hadn’t been playing with this a year ago.
  8. They’re on Rails.

Ruby on Rails: "it's fucking horrible"

This is a rare treat. Someone who actually gave Rails a good couple of hours, but couldn’t get anything done, and thus hates its guts:

Well, I’ve found this: it’s fucking horrible. Anyone who tries to convince you that it’s in some way an elegant and consistent way to create ‘web applications’ is entirely insane. It’s taking me hours and hours just to get the most basic of stuff done, and a lot of that time was spent wrestling with the hideous documentation and bizarre, frustrating syntax.

Now get this. Since he was unable to get something done quickly (too steep a learning curve), the poor chap wants to give Python and Zope a swing ;). Not an evil word about either, but the learning curve of the latter is not exactly known to be flat. Heh.

This thought on “pre-written code” is also pretty funny:

If you really must use lots of pre-written code (and hey, sometimes that is handy — a DBMS-agnostic interface, say) then get to grips with Pear for PHP.

That’s actually both a testament to PHP (you can get something done without using any external frameworks or libraries at all), but also an interesting reflection about a fair share of PHP programmers work (they don’t use or like “pre-written code”).

In any case, he’s frustrations were real. It would be nice to hear about them in specific so we can do something about it. Although, it does bring a smile to read “it’s fucking horrible”. It seems like we’ve made it all the way around the programmer spectrum with that.