I totally agree with that assesment of the market and the potential demise
of ColdFusion (unless Adobe goes open source with it, which may not be a bad
move). I also agree that a good commercial, off-the-shelf application will
support all of the common web server-side language out there. Autodesk took
a good approach using SWIG (www.swig.org) so that the core of MapGuide
Enterprise and Open Source is written once in C++ and then the web
interfaces and API hooks are output to PHP, Java and .NET for the customer
to choose their web extension flavor choice. They are not writing three
different versions from scratch.
Andy
"Jason Birch" wrote in message
news:5393047@discussion.autodesk.com...
cgountanis wrote:
> We are leaning towards PHP for the price, security, multi platform and
> open source features. Just a full recode is not really in our best
> interest at the molment. Now that Coldfusion is owned by Adobe it has the
> slickest reporting features and is far from Legacy. If Adobe Flash and
> Adobe PDF are Legacy then I would agree with that. The last thing I would
> use is ASP.NET since they change everything ever few years and the
> security can be broke by any eager 12 year old with an Internet
> connection.
At one point, web application developers could dictate technology,
primarily because the market was not mature and IT departments had not
standardised on particular platforms for web development. These days,
if you are not supporting ASP.Net or Java, you've entirely written off a
large portion of your potential market. Others will come in and fill
the hole you are leaving. PHP is a good technology choice, but it can
be a hard sell in larger organisations (don't even mention it at the
City of Vancouver).
Cold Fusion, though it has a reasonable feature set and is easy to use,
is suffering from a diminishing market share, and does not seem to have
advanced much in recent years. It also has not transitioned away from
being a tag-based scripting language as ASP and PHP have. And when it
was moved to a Java platform, it broke (in my mind) one of its core
differentiators: real-time debugging. This is why I think of it as a
legacy system. These factors, combined with severe problems with our
6.x to 7.x upgrade and the requirement to recode for MapGuide, mean that
we intend to go from seven installs down to two installs in the coming
year. We are only keeping those two to support an application that
we're stuck with because the vendor doesn't want to do a complete
rewrite. 🙂
I can't imagine that Adobe sees much of a competitive advantage in Cold
Fusion. It's not giving them many new sales or open doors, the major
competition is "free", and it's eating up developer resources they could
be spending elsewhere. I wouldn't be surprised to see CF abandoned
while Adobe concentrates on promoting a Flash-only web.
OK, that's enough "holy war" stuff for now 🙂
Jason