I doubt Adobe ever considered "snatching" the name. The Thermo team actually came up with the name (Flash Catalyst) themselves, persisted, and were very grateful when Adobe capitulated (unlike Apollo/AIR).
I can assure you most of us in the Flash community never heard of the "Catalyst Framework", so we'd never get to the next step of presuming that the word "catalyst" would be off the market.
I use Flash, and I'm also aware of Perl's "Catalyst Framework", which I also, uh, use all the time. I mean, um, they are both, uh, software projects aimed at uh, what's the phrase I'm looking for here, oh yeah.
They are both software projects designed to leverage object-oriented best practices and innovative programming concepts in order to facilitate rapid applications development on the web.
So, er, no confusion at all, uh, right?
(I like how you claim ignorance on behalf of an entire "community", as if that's some kind of excuse.)
Comments
I doubt Adobe ever considered "snatching" the name. The Thermo team actually came up with the name (Flash Catalyst) themselves, persisted, and were very grateful when Adobe capitulated (unlike Apollo/AIR).
I can assure you most of us in the Flash community never heard of the "Catalyst Framework", so we'd never get to the next step of presuming that the word "catalyst" would be off the market.
The real controversy is "Flash Builder": http://flashbuilder.net/
That's weird.
I use Flash, and I'm also aware of Perl's "Catalyst Framework", which I also, uh, use all the time. I mean, um, they are both, uh, software projects aimed at uh, what's the phrase I'm looking for here, oh yeah.
They are both software projects designed to leverage object-oriented best practices and innovative programming concepts in order to facilitate rapid applications development on the web.
So, er, no confusion at all, uh, right?
(I like how you claim ignorance on behalf of an entire "community", as if that's some kind of excuse.)