Tag: Ruby on Rails

Parents:

• Ruby,
• Web

Wednesday, December 17, 2008

1. Sam Ruby: Rack'em Up! I have only a feint idea what all that means, but I think it means it'll be easier to rewrite my web site in Ruby if I'd like to To finish reading.

     ¶ (0) Tags: [Ruby, Ruby on Rails]

Friday, January 25, 2008

1. #haml (via) - new templating language for RoR.

     ¶ (0) Tags: [Ruby on Rails, Templating]

Monday, September 24, 2007

1. 7 reasons I switched back to PHP after 2 years on Rails - O'Reilly Ruby (via). The main reason I'd hope to switch to Rails is not for Rails itself, but to be able to use Ruby. If only PHP used Ruby

     ¶ (0) Tags: [PHP, Ruby, Ruby on Rails]

Monday, July 30, 2007

1. Scale rails from one box to three, four and five (via).

     ¶ (0) Tags: [Ruby on Rails, Web Development]

Wednesday, July 25, 2007

1. Fleeting Ideas: Disambiguated URLs with Ruby on Rails (via).

     ¶ (0) Tags: [Ruby on Rails]

Friday, February 2, 2007

1. Ruby Reports (ruport). Check out acts_as_reportable

     ¶ (0) Tags: [Ruby, Ruby on Rails]

Friday, January 19, 2007

1. Rails 1.2 released. Woot.

     ¶ (0) Tags: [Ruby on Rails]

Tuesday, May 2, 2006

1. MonoRail:

   MonoRail (former Castle on Rails) is a MVC web framework inspired on Action Pack. The Action Pack way of development is extremely productive, very intuitive and easily testable.
   
   MonoRail differs from the standard WebForms way of development as it enforces separation of concerns; controllers just handle application flow, models represent the data, and the view is just concerned about presentation logic. Consequently, you write less code and end up with a more maintainable application.

     ¶ (0) Tags: [ASP.NET, Ruby on Rails]

Friday, April 7, 2006

1. Mike Clark: Running Your Rails App Headless.

     ¶ (0) Tags: [Ruby on Rails]

Monday, March 13, 2006

1. IBM developerWorks: Exploring Active Record.

   Active Record [is] the persistence engine behind Ruby on Rails. Active Record bucks many Java conventions, from the typical configuration mechanisms to fundamental architectural choices. The result is a framework that embraces radical compromises and fosters radical productivity.

   To read.

     ¶ (1) Tags: [Object-Relational mapping, Ruby on Rails, To Read]

Sunday, March 12, 2006

1. Lesscode.org has an enormous post on James Gosling's recent idiotic comments. DHH, creater of Rails has also has comments.

   Ryan at Lesscode concludes thusly:

   All we’re asking is that you stop spreading misinformation about the current state of dynamic languages to the press, analysts, and your customers. This does not require you to champion or otherwise support these technologies - just stop lying about them. One year ago, this type of behavior could be attributed to a lack of documentation and discussion on these issues, today it’s impossible to attribute to anything but malice.

     ¶ (0) Tags: [Java, Programming languages, Ruby, Ruby on Rails]

Tuesday, December 13, 2005

1. Rails 1.0: Party like it's one oh oh! (via Sam Ruby). Rails 1.0 released!

   Update: David has an announcement and rubyonrails.org has a new site with more content. Check out the quotes about rails.

     ¶ (0) Tags: [Programming, Ruby on Rails]

Tuesday, November 29, 2005

1. "Instant Rails is a one-stop Rails runtime solution containing Ruby, Rails, Apache, and MySQL, all preconfigured and ready to run. No installer, you simply drop it into the directory of your choice and run it. It does not modify your system environment." Nifty!

     ¶ (0) Tags: [Programming, Ruby on Rails]

Thursday, November 24, 2005

1. Evaluation: moving from Java to Ruby on Rails for the CenterNet rewrite (via John Wiseman). To read.

     ¶ (0) Tags: [Java, Programming, Ruby on Rails]

Wednesday, November 2, 2005

1. ZDNet: Ruby on Rails chases simplicity in programming (via Steve Dekorte), an interview with Hanson (to read).

     ¶ (1) Tags: [Programming, Ruby on Rails]

Wednesday, October 12, 2005

1. PragDave: Is Ruby Better Than ...?:

   ... I’d rather write in a language that let’s me focus on the application, and which lets me express myself clearly and effectively. And, if I can do those two things, I believe that sometimes I’ll be able to write code which is cleverer than something I’d write in a lower-level language. A better algorithm will easily gain back any marginal performance hit I take for using a slower language.
   
   Justin Ghetland experienced this recently on a Rails project. Having coded the same application twice, once in Java and once using Ruby on Rails, he was surprised to discover that the Rails application outperformed the Java one. Why? Justin believes it’s because Rails does smarter caching. The Rails framework contains some very high-level abstractions, and that allows the folks writing the framework to be smart about what they do. They accepted the linear hit of writing in a language that executes more slowly because they got a non-linear increase in speed from being able to write better code.

   Similar point covered earlier.

     ¶ (2) Tags: [Java, Ruby, Ruby on Rails]

Saturday, September 3, 2005

O'Reilly Network: Ruby on Rails: An Interview with David Heinemeier Hansson

O'Reilly Network: Ruby on Rails: An Interview with David Heinemeier Hansson, via LtU. I liked citylight's comment on LtU entitled "ActiveRecord and the relational model". Why is it exactly that we can't use relational algebra directly instead of SQL, especially since RA is used internally in query optimization?

Update: I particularly liked this part of the interview:

It's hard enough to solve your own problems with eloquence. Trying to solve other people's problems is damn near impossible—at least to do so to the level of satisfaction that would make me interested in the solution.

That's why we hold the notion that "frameworks are extractions" so very dear in the Rails community. Frameworks are not designed before the fact. They're extracted when you've proved to yourself that an approach works. Whenever we get ahead of ourselves and try to leap over the extraction process, we come back sorely disappointed.

Permalink | Comments? | Tags: Programming, Ruby on Rails | id 7273

11:15 (utc-5)
edited: 22:45 (utc-5)

 

Thursday, August 25, 2005

1. I need some spice in my programming life. After reading Sam Ruby's most recent post about Ruby on Rails, I think it's time for me to learn Rails. It'll be a good exercise for me to gain some intimate knowledge of Ruby as well.

     ¶ (2) Tags: [Programming, Ruby, Ruby on Rails]

Tuesday, August 9, 2005

1. Sam Ruby: Rails Confidence Builder. Sam builds a simple Rails app.

     ¶ (0) Tags: [Programming, Ruby on Rails]

Saturday, April 16, 2005

1. Bill Katz: Could Rails have been built without Ruby?

     ¶ (0) Tags: [Programming, Ruby, Ruby on Rails]

Tuesday, July 27, 2004

Conventions over configuration

Yesterday I watched some of the Ruby on Rails videos. One of the most interesting design principles I got out of it is that it's better to make things flexible by convention rather than by having to manually configure everything. Naming conventions mixed with reflection can often be every bit as flexible as configuration, yet it's far simpler and more maintainable because you DRY.

Permalink | Comments? | Tags: Programming, Ruby on Rails | id 5035

15:55 (utc-4)