Post a message

Ruby On Rails is the fashionable way of developing web applications at the moment. But if you’ve never used Rails, it is not at all obvious how to get started with it. In this article, I’ll explain how to create a first Ruby On Rails application. First Install Ruby and Rails… This tutorial assumes that you have both Ruby and Rails installed. Furthermore, it also assumes that you have a passing familiarity with the Ruby language. For a guide to installing Ruby and doing (...)

I am genuinely and honestly intrigued (and baffled) by the passion you feel about this. The expression "not how it should be done" implies that there is, somewhere, an inviolable law which dictates this stuff. Similarly, "Designers don’t want as little code as possible in their views". In my experience, people who do design professionally don’t want any program code in their HTML. In fact, I have yet to meet a full-time professional designer who works with Rails and I doubt if many would wish to. Put simply, RHTML design and Dreamweaver don’t really go together! I’ve worked with graphics (page and web) designers for most of my professional life - the last 20 or so years in the computer publishing industry. I’ve never yet met a single one who knows any programming of any description, and I really wouldn’t like to imagine their response if I told them they needed to learn Ruby!

I must admit that I am more than a little sceptical about the apparent conensus of opinion regarding MVC. I maintain that it is no more messy to put linebreaks into Ruby code than to mix Ruby code into HTML. To me, this fact is so obvious that I can’t see how it can be denied. Similarly, I don’t understand is why you would have me believe that mixing HTML into Ruby is bad but Ruby into HTML is good. The logic escapes me.