> Even if Adobe completely kills Coldfusion (which they won't because they're
> already making BIG plans for the next version (coming out sometime next
> year). Anyway, even if they do kill CF, there'll be Coldfusion jobs for
> YEARS to come due to all of the existing websites that use it. Besides, even
> if Adobe is foolish enough to get rid of CF, SOMEONE would come along and
> buy it from them.
I'm not sure about that. It's probably true, but again, I'm just not
comfortable with probably.
> I'm not worried about CF going anywhere. At least it has the benefit of a
> single company with a huge marketing budget. I'd honestly be more worried
> about PHP going somewhere than Coldfusion as PHP has no central
> company/organization that "owns" it, therefore no single company which has a
> real investment in it's longevity.
Well.. that's the eternal open vs. closed question, and one which we
won't solve today. I think we're just going to have to disagree on
this. I believe that a dedicated developer community working together
can create stable, useful and long-living software. I don't believe
that a marketing department is necessary if the code speaks for
itself. And I don't believe for one second that having one company
"own" a platform is a good thing. PHP isn't "owned", but do you think
Yahoo would let their programming language of choice go away? Nor
would any other of the many large corporations who rely on PHP every
day. So in effect a successful open-source product like PHP or even
Apache, is being looked after by an army of interested companies and
individuals. And, since no one entity "owns" it, it can not be killed
by one person or company, thus eliminating the single point of
failure. I know CF has a very vibrant user base and many large
corporations use it, but they would have NO say if Adobe decided to
kill it and take the copyright to their grave. But again, this is
just my opinion.
> You say that you don't like CF because of the code? That's absolute
> nonsense...I'm all for coding, I really enjoy it too, but WHY write an extra
> ten lines (or more) of code when you don't have to? Do you rewrite your
> Replace function every time you use it?
It's just personal preference. foreach($array as $key => $value){...}
just makes more sense to me. It's that simple. Writing in tags is
great too, I just prefer the syntax. I prefer Ruby to PHP, but that
doesn't make PHP bad... I just like Ruby better. I don't like feeling
like my hand is being held, and for me CF does that. I was never very
advanced in CF so I never got into writing custom tags or any of that
stuff... so I could have a misconception there, but I'm just sayin'...
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
