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... ______________________________________________________________________ Alex Duffield . Principal . InControl Solutions . http:// www.incontrolsolutions.com On 15-Feb-07, at 7:59 AM, Thomas Fuchs wrote: > > A bit harsh, but tentatively agree. It's a really great way to get > into it. > > Once you'll see how easy it is to do dynamic/ajaxified pages with > Rails, you'll start to get more curious about what goes on "under the > hood". > Of course, the real power of Prototype will only then start to > unfold... :) > > Best, > Thomas > > Am 13.02.2007 um 19:29 schrieb Phlip: > >> You seem to be missing "Rails" in that mix. One should never code JS >> directly if one can use a unified and flexible platform that runs it >> for you. Learn Rails, and your websites will be completely dynamic >> before you know it. And you can then view the generated source, and >> learn how Rails put the effects together, to learn Prototype. >> >> Ruby on Rails is the path of least resistance here... > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
