Sure ... ramble on and don't give me a link to COAL... is that a CF project or what?
John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Rawlinson Sent: Thursday, September 22, 2005 8:29 PM To: [email protected] Subject: Re: [Spam] Re: [CFCDev] Ruby on Rails for CF Im not sure if Im in a minority of the people on this list but I work for a small company that does custom development for others. We don't do much development for in-house purposes. Because of that structure to our business I am constantly learning new languages/frameworks/methodolgies etc. One day I could be developing in ASP.NET the next in CF then Java, then C++, then over to PHP, throw in some Ruby as of late and back again. It all depends on the customer, their needs, budget, desires, etc. I like RoR. I think it is pretty slick. If for no other reason it is super easy to get a working prototype up and running. Even if Ruby isn't the language you'll be using for the final product; a working prototype helps us understand the requirements better than any series of meetings ever do. I think port of Rails to CF is a good idea. There is a PHP rails effort underway. Obviously there is a Ruby version. A big part of the reason RoR has gained so much popularlity of the past year is because it is pretty well thought out and put together. I don't know how the Rails CF framework would be extended to support other frameworks such as Mach-II or Model-Glue - but if it could be that would be pretty darn cool. Though, I think from a developing perspective the mingling of methodologies in one project could get confusing and become troublesome from a maintenance perpspective. I think things like the GEM system (in ruby) and PEAR (in php) are pretty cool for helping keep people, and their frameworks, up-to-date. I think that would be, at this time, and even bigger benefit to the community. I'm not sure if that is what COAL is trying to do and if not that is a project I would be more wiling to get involved with in my spare time than the development of another framework (even though I think Rails is cool as all get-out). Well, sorry for rambling. Bill On 9/22/05, Roger Lancefield <[EMAIL PROTECTED]> wrote: > Gary Menzel wrote: > > Do you stiffle progress for stability? > > Well, if such a stark choice had to be made, I'd go for the option > that would deliver the most benefits, and right now for me at least, > consolidation is preferable to progress. Ignoring my own situation, > I'm willing to bet that the average developer is better off > fine-tuning what they have now, rather than rushing off to jump on > the latest acronym bandwagon. (The guys I know who have done the > most innovative work and have been most productive using CF over the > last few years were still using v5.0 as of late last year). > > As for sticking with what you know. Well yes, many will, but that's > not a solution for a shrinking community. > > I understand that there's a tension between the benefits of > stability and the inevitability of change. All the same, as far as > the perfect framework goes, there never will be one -- and that was > behind my comment about the perfect being the enemy of the good. I'm > willing to bet that someone who can't make today's framework work > for him/her will have just as many issues with tomorrow's :) > > I'm not so much attempting to be King Canute, rather just > questioning both the pace and value of the rate of change. > > John, have just seen your latest posting. Thanks for your response. > > > Gary Menzel wrote: > > Do you stiffle progress for stability? > > I would think if there was a "perfect" framework out there, then there > > would be no need to develop new ones. Just like if there was a perfect > > coding language we wouldn't have the choice we have. > > But there is no perfection - only continual improvement. > > There is a simple solution though - just stick with what you have if it > > works for you, but if it doesn't work then build something new. > > Regards, > > Gary > > > > > > > > ---------------------------------------------------------- > > > > You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. > > > > > > > > CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). > > > > > > > > CFCDev is supported by New Atlanta, makers of BlueDragon > > > > http://www.newatlanta.com/products/bluedragon/index.cfm > > > > > > > > An archive of the CFCDev list is available at www.mail-archive.com/[email protected] > > > > > > > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). > > CFCDev is supported by New Atlanta, makers of BlueDragon > http://www.newatlanta.com/products/bluedragon/index.cfm > > An archive of the CFCDev list is available at www.mail-archive.com/[email protected] > > > -- [EMAIL PROTECTED] http://blog.rawlinson.us If you want Gmail - just ask. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
