De nada, Alex. :)

I've been committed to blogging once a week, usually on Thursdays (in fact, I just blogged twice today). And I'm committed to continue doing so. I'm having so much fun with Rails, Ruby, and related topics, and learning so much, that there's always going to be something to blog about (if anything, so I can keep track of my findings). :)

So, whoever's interested in that, please subscribe to my blog at www.lassala.net


>Hi Claudio,
>
>Obrigado for the reference to your blog. Please keep placing references here when you add comments to the blog (frankly to keep the category alive and interesting).
>
>It's especially significant to me and perhaps to others who did not go the .NET route to see that one who became quite proficient in .NET finds value in Rails.
>
>Cheers,
>
>Alex
>
>
>
>>I've been messing with Rails for a couple of months now, and am working on an actual project. Having lots of fun. I'm blogging my experiences with it:
>>
>>http://claudiolassala.wordpress.com/tag/rails/
>>
>>
>>>Hi,
>>>
>>>For a little while now I've been reading up on Ruby on Rails, a very interesting Web development framework. I am not an expert, only a curious person so far, but am going to try to bring here some information about the product and why it got me interested. Often I'll quote from a Rails site or book since it will be more correct than my attempts.
>>>
>>>Rails was extracted from an application (Basecamp) developed by David Heinemeier Hansson around 2005. It is open source, free software, now in version 3.0. The best part is not that it is free, nice as that is, but that it has very powerful approaches at the core and that it has developed a very vibrant community around it. As we know from our experience with FoxPro, the community can be a feature of a product. That is why I asked Michel to start this section for Ruby on Rails. I think people here will find it an powerful and appealing product.
>>>
>>>Rails makes certain assumptions about the type of data based applications that developers often write and provides the means to go about it very quickly, yet allowing wide ranging customization later. All Rails applications are implemented using the Model-View-Controller (MVC) architecture. All Rails applications have testing support baked right in. It has a number of powerful approaches at the core. The one I like best is "Convention over configuration". If you accept their conventions, you can save A LOT of time.
>>>
>>>Here are some references:
>>>
>>>http://rubyonrails.org/
>>>http://rubyonrails.org/applications
>>>http://guides.rubyonrails.org/
>>>
>>>I think it is really worth your time to investigate this product.
>>>
>>>Alex