[consulting] Drupal considerd dangerous

Khalid B kb at 2bits.com
Sun Dec 24 20:50:35 UTC 2006


I can't comment on the specifics of the case you mentioned, since there is
so little mentioned as to what went wrong, why it went wrong, ...etc. As
much as I want to respond to that part, there is not much to go by here.

However, you are making a worse mistake by saying that you are "waiting for
a Ruby solution for your needs".

None of the issues you (or Evan or others) alluded to are
technology/platform based, yet, you think that another technology/platform
is the cure-all for your ills.

Choosing a solution for its technology, and not based on business needs, is
BAD BAD BAD, and can only lead to problems. Clients care less if your
solution runs on COBOL and uses flat files. What they care about is features
THEY can use.

So, please be more specific and you will get a responds to that, and do not
fall into "technology X is sexier than technology Y" trap.

On 12/24/06, Kaliya * <identitywoman at gmail.com> wrote:
> Even,
>  I am with you on this. I find the community attitude quite arrogant and
> condescending.
>  I am quite familiar with one of the startups 'hurt' by the choice to use
> Drupal.  It was a mistake and they and  likely several of the startups that
> choose Drupal as a base were sold on the platform really hard by people in
> the community.  It was pumped up to be more then it was and they bought it
> and then got into it and it just was a mess.
>  All I wanted to do was nice clean simple neat social networking for
> spiritual leaders and groups. Without a  whole lot of cost and I couldn't do
> it in Drupal.  I personally am waiting for a Ruby solution for my needs.
> =Kaliya
> On 12/21/06, Evan Leibovitch <evan at telly.org> wrote:
> >
> > Kieran Lal wrote:
> > >> There are no qualifications or "it's not always the best choice" type
> > >> honest comments anywhere to be found.
> > >>
> > >
> > > By targeting specific uses we tried to highlight it's strengths.
> > > Highlighting weaknesses is not very useful as it's frequently the
> > > limitations of the users ability to use a tool that are the real
> > > weakness.
> > >
> > Well, there we have it: "There are no weaknesses in Drupal, just
> > weaknesses in users' ability to master it."
> >
> > You have me at a loss for words, I honestly have no answer to something
> > so incredibly arrogant.
> >
> > >> Small businesses are explicitly mentioned as a target group for whom
> > >> Drupal is the right answer.
> > >> In fact, the page offers no realistic appraisal of what Drupal
> > doesn't
> > >> do well, which is also what people coming to such a page are
> > >> looking for.
> > >>
> > > What do you suggest?
> > >
> > The kind of honesty that Bill suggested. An acknowledgement that Drupal
> > isn't for everyone, and a frank analysis of its advantages and
> > drawbacks. Respect for users' intelligence rather than contempt.
> > Emphasis on understanding what users need, rather than what you expect
> > of them.
> >
> > - Evan
> >
> > _______________________________________________
> > consulting mailing list
> > consulting at drupal.org
> > http://lists.drupal.org/mailman/listinfo/consulting
> >
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20061224/16a64cc1/attachment.htm 

More information about the consulting mailing list