Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Programming IT Technology

Rails Day 2005 a Success! 26

zestyalbino writes "Rails Day 2005 has finished! In total, there were 55 entries that qualified. Descriptions and downloads are on the site. For those of you that don't know, Rails Day was a contest to see what websites entrants could come up with in just 24 hours using Ruby on Rails."
This discussion has been archived. No new comments can be posted.

Rails Day 2005 a Success!

Comments Filter:
  • Next year (Score:4, Informative)

    by lastninja ( 237588 ) on Monday June 06, 2005 @09:20AM (#12735085)
    I bought the (beta) book Agile Web Development with Rails [pragmaticprogrammer.com] a week ago. So far Rails looks like a really cool web framework. Who knows perhaps will I participate in next Rails Day 2006.
  • by Marillion ( 33728 ) <ericbardes@gm[ ].com ['ail' in gap]> on Monday June 06, 2005 @10:03AM (#12735523)
    I know some of those from Cincinnati who where participating in Rails Day. Here are some links to their blog entries ...

    Mark Windholtz [blogspot.com] - Member of Team 32.

    Jim Weirich [onestepback.org] - Member of Team 8.

  • Having recently tried out Rails, starting from zero knowledge of Rails and some knowledge of Ruby, it's the closest thing I've found to a productive web framework.

    I'd be interested in recommendations for Java frameworks which can provide similar productivity, however. (Much as I like Ruby, it's still a tough sell in the corporate world.)
    • Give Trails a try. It's built on Hibernate, and it's still a whole lot more verbose than Rails, but it's probably the closest thing.

      I'm glad I work in a company where they just ask me to write the app and don't really care what it's written in. I could write my apps in APL, though they might have kind of a problem with that after the fact. If I had to ask to use Ruby, they'd probably say no, no one else uses it, but if I say "I wrote it in Ruby", they'll hear "I wrote it" first, then I just tell them th
      • The problem is hosting. If Ruby compiled to the JVM, there wouldn't be a problem, but getting a secure sandboxed Ruby web server with clustering is an unsolved problem right now.

        There's also the issue of who can maintain the application after I'm gone. There's something to be said for having a solution that runs on a RAIJP array (Redundant Array of Inexpensive/Interchangeable Java Programmers).
        • There's something to be said for having a solution that runs on a RAIJP array (Redundant Array of Inexpensive/Interchangeable Java Programmers).

          First of all, I nearly spit coke into the keyboard.

          Secondly, ain't that the truth. I design software for a living, and instead of designing for a platform, or a CPU architecture, I have to optimise for maintainability. So I design to a RAIJP.

          In a Fortune 500, they make sure they have lots of replaceable cogs in the machine, so I have to design to the LCD.

    • Selling Ruby in the corporate world is easy [google.com]. Just tell them this:

      Ruby has the momentum to leverage the dynamic potential of synergies between your skillsets and its core competencies on Internet time. Achieving best-of-breed, mission-critical componentization utilizing standards-compliant scalability, it provides an adaptable, standards-based framework to add value via a fast-track, result-driven development process.

      :-)

  • i'll buy that when i see a high traffic site like /. written in it.

    i tried a version a few months ago and it didn't work all that great with PostgreSQL...
    • Any chance you can be a bit more specific about what "didn't work great with PostgreSQL"? I use it with postgres, and it works just fine. Maybe I just haven't run into the issues you did. Also, why wouldn't you think that it could handle larger traffic sites?
      • it didn't create the form fields in the order specified. granted, it could be a bug then and no more today.

        still, i find it a bit worrysome to let a web framework handle all database stuff for me.
    • High Traffic? CDBaby is working on a new site in Rails. ODEO will be launched soon. 43Things.com is based in Rails.
    • To name just a few really busy rails driven sites:

      http://www.basecamphq.com/ [basecamphq.com] Tens or thousands of users

      http://www.backpackit.com/ [backpackit.com] Thousands of users

      http://www.43things.com/ [43things.com] Big enough for Amazon to care

      This is of couse ignoring all the private rails apps used internally by some pretty decent sized companies.

      Rails scales amazingly well on lighttpd with fcgi Apache with fcgi does a pretty good job as well.
      You can run it on Linux, FreeBSD, Windows Server 2003 and just about any other respected(I use
  • A bunch of people posted specific projects to try out on my blog:

    rails day projects to try [robbyonrails.com]
  • Ok, so I was into rails between 0.7 and 0.9 or so. But I went back to PHP for three reasons.

    1. The libraries are thoroughly tested.
    2. It's easier to deploy.
    3. I trust the underlying stack.

    But I learned a LOT from rails, and I use rails-style controllers and models in PHP, although I handle the relations manually. I think rails is a reminder of what a good application of design patterns gives you, but it's not the be-all and end-all.

    Oh, and I did my own "PHP day" mad scramble with the idea I had for Rai
    • Rails is not that great as hype may make you think, but PHP is a big pile of crap.

      besides, Ruby is far better and expressive a language than PHP.
      • PHP, the language, is not my favorite thing to work in. But it's not too bad when you're working in PHP 5, which has good OOP and XML support.

        But PHP is expedient. If it gets the job done quicker, with less headache, while still letting me use best practices and design patterns, I'm all for it, obnoxious function naming be damned.

The optimum committee has no members. -- Norman Augustine

Working...