Comments on: Rails Furthers Industry Acceptance

by: Candide

Sun, 13 Aug 2006 22:02:28 +0000

Of course, the bane of less code is that you have no clue what’s going on when push comes to shove.

I’m running into this problem right now with adding a column to a development project I’m working on: I’ve updated my database, added a new column, re-created the scaffolding through the generator, and…nothing. Nix. Nada. That column (book_id) simply refused to show up.

The answer? Change the name of the column. For some reason, the scaffolding REALLY did not care for the “book_id” column. I’d like to know where that is in the documentation.

by: Freedom vs. Safety [@lesscode.org]

Thu, 25 Aug 2005 18:44:43 +0000

[…] The advocates of freedom languages tend to talk first about the speed and efficiency of the individual programmer. They discuss the expressive power of different constructs and focus on all the powerful features that the safety languages lack. They point out complex patterns and show off twenty-line systems that do the same thing. They talk more about the ease or purity of things than the safety of things. They are dismissive of static-type-safety and compile-time validation in general. […]

by: blogx » Blog Archive » LISP

Thu, 11 Aug 2005 22:44:56 +0000

[…] Interesting reading this morning about a language that was written in 1958 called LISP, and is the powerhouse behind all those airline search engines out there. Got there from a mention on the list about Ruby on Rails that led me to one of Ryan Tomayko’s articles about less code. The song remains the same. […]

by: Ryan Tomayko

Tue, 19 Jul 2005 14:55:49 +0000

So what is it exactly that you are doing about having “a hard time reporting on all the recent Rails press”?

Ahh, well, I've been conversing with a few really solid Ruby and Rails developers trying to get them to come on board with lesscode.org. That way I don't have to worry about being fair and balanced because there will be someone concentrating on covering the Ruby community. In fact, I've spoken to people from the Perl, Python, PHP, and Ruby communities as well as some general web architecture guys that understand why these tools were built the way they were.

The interest seems to be there but everyone has two or three weblogs + columns at this point. I've not given up hope completely, we'll just have to wait and see.

by: John Speno

Tue, 19 Jul 2005 14:06:35 +0000

So what is it exactly that you are doing about having “a hard time reporting on all the recent Rails press”?

by: Dannno

Sat, 16 Jul 2005 13:15:07 +0000

Waxy posted a link to Django Django yesteday which purports to be Rails for Python, though, being unfamiliar with Python, I was unable to assess the claim (No offense Pythoners, I just don't jive with the syntax, like I don't jive with Lisp's syntax).

by: PJ Hyett

Sat, 16 Jul 2005 01:31:17 +0000

That article (and specifically the code example you’ve posted) was one of those beautiful occasions when it becomes perfectly clear that the Java folks that continually put down Rails need to eat crow. The KISS method comes to mind.

by: Jordan Cox

Fri, 15 Jul 2005 20:09:02 +0000

I always try to learn as many languages as possible. For me, Ruby on Rails was a great chance to dive into Ruby - and I'm glad I did. It's a very robust language, that's still very simple - and has finally gotten this gr(e|a)y procedural programmer to fully embrace OO. :)

Seconds on the great blog comment. I love it. The design is wonderfully different - and I love the concept. Keep it up!

by: ludo

Fri, 15 Jul 2005 10:04:11 +0000

I think may Python lovers are in my same situation, having postponed learning Ruby for a while in the hope that a Rails-like framework for Python would eventually get developed. Unfortunately it looks like we will have to learn Ruby, or find the time to develop PyRails (which will involve learning Ruby anyway).

BTW, great blog!