Hi All,

As the reactions to the Macworld review continue to resonate, I am feeling a sense of deja vu (& some worry) as I read suggestions that the way to deal with the perceived prejudice against HyperCard, XTalks in general, and Revolution by extension is to build the best application one can AND TAKE PAINS TO HIDE ITS REVOLUTION ROOTS.
.
IMFO, the reason we are having this discussion today is because so many of the people who authored excellent HyperCard applications chose to follow that route rather than to confront the data processing developer & editorial communities with their ignorance ten years ago.


A significant portion of list members are professionals whose general experience in the field & technical knowledge is many times greater than the critics & that portion of the rest of the dp community that is foolish enough to rely on those critics rather than doing their own homework.

In my experience, the later usually turn out to be VERY unsatisfactory (and often dissatisfied) clients. However, if you want to do business with them, you're going to have to reeducate the reviewers first. It can be done. I'd love to see Andy placed in a position to list the "ambitious" projects that cannot be accomplished with Runtime Revolution.

For those of us who would rather choose a non-confrontational stance, there is still one thing you can do to fight the legacy of X-Talks prejudice:

DISPLAY THE MADE WITH RUN REV IMAGE ON EVERY APPLICATION YOU RELEASE!

If you run away from the issue and try to hide you applications' roots, your efforts can only work against the long-term success & acceptance of the platform you use to build that application.

Rob Cozens
CCW, Serendipity Software Company
http://www.oenolog.net/who.htm

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to