There are probably many reasons to purchase Metacard. I purchased Metacard for two reasons: (1) *I* want a rapid, cross-platform development tool that (2) actually works. While the world flails away with the almost useless Java, a tiny company develops and markets a truly functional, cross-platform tool that works, and it is a user-friendly scripting (x-talk) programming model rather than the user-unfriendly c++ syntax favoured elsewhere. For many reasons (mostly, though, that hypercard still handles anything my lab needs, and the need for cross-platform functionality in my lab has not yet reached the pressing point I anticipate for the future), I have yet to do much with Metacard (other than to proselytise its virtues to colleagues), but I will continue to support it by updating my licence when my current subscription runs out, just so such a tool will be there when I *need* it. John R. Vokey > From: [EMAIL PROTECTED] > Reply-To: [EMAIL PROTECTED] > Date: Sat, 30 Oct 1999 09:10:23 -0700 (PDT) > To: [EMAIL PROTECTED] > Subject: Digest metacard.v003.n120 > >> As it was suggested, the best approach is to download the demo and >> experiment, see how far MC goes in terms of features and performance, or >> just trust blindly all the advice you got so far and go for it... and >> decide latter. > > With this I definitely agree. I spent several months trying to decide > whether to get MetaCard. I was coming from SuperCard. I finally took the > plunge, without having reached certainty. Now, several months later, I > know it was the right choice, but I couldn't have decided that without > making the commitment and starting the conversion process. You can start > this with the demo, but I would suggest checking the specs, and if they > meet your requirements, go for it.
