Alex Duffield wrote: > Well, as much as my limited dabbling has permitted, rails looks very > cool, but I find it unrealistic to switch all my development over to > rails simply because its cool. > > When I take over a site for a new client, quite often they are > reluctant to move to a new ISP, as that causes them to have to update > all there mail settings and such.. > > I chose PHP/MySQL way back when because 95% of ISPs already offer it. > > as for " One should never code JS directly" I find this as silly as > someone saying one should never code HTML when you can use an app > like Dreamweaver...
I find it silly that you rejected my premise for irrelevant external reasons, then accused my conclusion of lacking a premise. Nobody told you to switch all your clients' sites to Rails. You then extrapolated that to claim I told you to move all your clients to new ISPs. Etc. Write a scratch Rails project, put form_remote_tag in it, and get that to work. With the right tutorial (such as the Agile Rails Book), you could do all that in 15 minutes. Then hit View Source and look at the generated code. Install Firebug, run the site, and read its transactions. Next, never write specific code in a low-level language - HTML, SQL, JavaScript, etc. - if a high-level generator is available to integrate that code with your domain objects, and produce generic code. If such a generator is not available, for external reasons, then by all means write the code in the low-level language! -- Phlip http://www.greencheese.us/ZeekLand <-- NOT a blog!!! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
