|
|
Posted by shimmyshack on 09/03/07 23:04
On Sep 3, 11:09 pm, Sanders Kaufman <bu...@kaufman.net> wrote:
> Dawson wrote:
> > I found your reply useful and it's of the same opinion as mine,
> > however, I'm fighting against an agency who disagree, so, I need to
> > find sources or a case study to prove why Joomla is not up to the job
> > of an enterprise application.
>
> Evangelists. Yuck. They decide the wrong way - from the goal to
> supporting facts, instead of t'other way 'round.
>
> It sounds like they've already decided on Joomla, and are now actually
> looking for support for their predetermined goal.
>
> For my two-cents worth, here's a buck.
>
> It sounds like you might consider turning it around and asking the
> "agency" that pronounced Joomla to be an "enterprise application" to
> back up that claim. (Good luck with that.)
>
> Bear in mind, that it's a framework for building applications, and not
> an application unto itself. Whether you go with Joomla or build an
> in-house solution, the enterprise will still need to keep a development
> staff on hand - and they will be busy.
>
> Bearing that in mind, consider further that that staff will all have to
> be Joomla specialists - a very time consuming requirement since Joomla
> is a very BUSY Open Source project and *constantly* changing, often in
> very dramatic ways. The current version is called 1.5, but is really
> just one of a dozen or so releases put out in a very short time - some
> buggier than others.
>
> Finally, it's worth re-emphasizing that even though Joomla markets their
> product as a being usable in creating "complex corporate applications",
> it is not an EA unto itself
>
> What they're doing there is what I call "stealing legitimacy" from a
> foundation component - strictly for marketing purposes. In fact, it is
> PHP itself that makes EAP development so doable - and not Joomla.
one of the very first php servers that I had to clean up following a
worm was acked through joomla.
nice software to be sure, but for enterprise you are talking proper
security, code auditing, stability, fast patch time, business support,
one of the things enterprise IT guys fear most is a constantly
changing code base, and they mistakenly think open source means wide
open to busy fingers meddling with it. Joomla would be very hard to
force into shape, and you would be left with a code of files that
would quickly be outdated and unpatchable from the Joomla source
unless you used SVN/CVS to update parts of the codebase left after you
had modified it for your use.
I cant understand anyone suggesting that a piece of software is
enterprise level... what does it mean... surely enterprise is much
more than the software, its whether it is scalable whether it
integrates into the existing business, do you already have php
servers, or in house php experts, will it run on apache, do you all
understand how to secure apache, or will that have to be outsourced.
IMHO agencies tend to steer biz towards what the agency can support
and away from what the biz has skills to support for obvious reasons.
Navigation:
[Reply to this message]
|