The biggest thing macromedia did was to have "instant generation" of flash and better use of exterior executables. However, some of the best reasons to use CF4.5 ENT didn't get much flushing out; writing "plugins" for CF became more taboo and Macromedia didn't endorse them nearly as much, which was a pain in the ass because it meant you had to craft your own widgets rather then easily share codebase.
However, the integration of management of flash, improved browser detection and layout rules, RSS support & management, and a few other features did help the product as well.. but the most important parts have went largely unchanged. CW -----Original message----- From: warpmedia [EMAIL PROTECTED] Date: Mon, 18 Apr 2005 13:14:10 -0500 To: The Hardware List hardware@hardwaregroup.com Subject: Re: [H] Who knew? Adobe buys Macromedia > This much I knew since I was a CF developer up till the 4.5 version in > 2001, I was wondering what Macromedia had done to it since and then what > would adobe would do with it. > > CW wrote: > > Oh, I still have lots of apps that are exclusively cold fusion. > > > > Cold Fusion's biggest benefits had nothing to do with Java, and everything > > to do with the integration of multiple SQL sources to multiple SQL outputs, > > including a much cleaner implimentation of access to Oracle then most ASP > > offerings. > > > > CW > > > > -----Original message----- > > From: warpmedia [EMAIL PROTECTED] > >> > >>Adobe cold flash giving you hot flashes? Guess CF is going through > >>menopause! > >> > >>What does either company have that can replace Coldfusion Thane? I've > >>been out of the loop for 4 years but know that CF as a service run under > >>java based MX(?) app server now and that job offers requesting CF skills > >>are few & far between these days. > >> >
