A painting of me

"In the meantime I stand by my claim that [ruby's] not appropriate for every situation." ⇒

   12 September 2006, early evening

Talk about not wanting to rock the boat. That's a pretty vacuous statement.

This is a post from my link log: If you click the title of this post you will be taken the web page I am discussing.

Perma-Link  

Comments

  1. I tried ruby and/on rails for a while. The framework lets you get CRUD apps up very fast (as long as you’re making a new database/table and follow their naming conventions, otherwise you have to spend some extra time editing more bindings etc).
    The number of files you have to edit to get something done, though, piles up. A change which would be simple in idea might require a dozen changes accross multiple files etc. This isn’t really THAT uncommon (eg if you use Spring or Hibernate or something like that), but it just means that it doesn’t REALLY make things THAT much easier. Just lets you write small crud apps really fast after you get used to it. At least that’s my viewpoint.
    Ram when you going to make something with Ruby on Rails? Before or after the Summer of T-Shirts? lol

  2. It’s looking like it will happen after the summer of T-Shirts. I never know what to make as well which is part of the problem. I was thinking of making something that I could use to coordinate stuff I want to do with my friends. Like a communal address book events planner sort of thing.

Don't be shy, you can comment too!

 
Some things to keep in mind: You can style comments using Textile. In particular, *text* will get turned into text and _text_ will get turned into text. You can post a link using the command "linktext":link, so something like "google":http://www.google.com will get turned in to google. I may erase off-topic comments, or edit poorly formatted comments; I do this very rarely.