Actually, we've had problems with this phenomenon here. A new project manager who's never heard of the product and wants to switch to ColdFusion or ASP.net because of Witango's "declining market share", unstable ownership history, "lack of resources", etc., but who does have the ear of management, had a large part in us not getting the upgrade to W5 when it first came out. It didn't help any that an affiliated campus who had many of their sites in Tango converted everything to other products in the same time period.
Of course, every problem we have with Tango2000 bugs or server problems simply reinforces his view. The last I heard, he felt that the Witango5 version is "merely catchup" to other webserver products on the market. Mind you, he doesn't have to do the dev work, if you know what I mean. He seems to simply not believe that the Witango dev studio is any better than the other guys' stuff. It's a moot point at the moment, because our budget's been cut so deep that we're not upgrading any of the web stuff for a while (web apps are a relatively new and minor area for us). But I may be asking y'all for help down the road when things aren't so tight. My lack of experience with web tech makes it very difficult for me to argue the point cogently. Currently I'm hoping that Witango's (and resellers') efforts to hit the trade shows & etc. will produce some reviews/awards/whatever that will impress him. > -----Original Message----- > From: Steve Smith [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 10, 2003 10:21 AM > To: Multiple recipients of list witango-talk > Subject: RE: Witango-Talk: What to call it > > > Two excellent points! > > I remember getting into a discussion with a co-worker about > 'technology'. He was concerned about what was then the Tango > product and it's lack of exposure. My stand was that most > clients don't care what the technology is that delivers their > solutions but they have been trained to ask by consultants or > competitors. Quite often it's because these > consultants/competitors have their own agenda. When you think > about it, when we're in a bidding process, the solutions > being pitched by them and us should be the same. Therefore > they are not wrong in trying to find a way to separate > themselves from us. If they are using a better-known tool, > they do it by pointing out that their tool is much better > known and recognized in the industry. > > Don't most of us do something similar? How many have tried to > use the 'not truly cross-platform' angle when speaking about > solutions developed in ASP/.net or CF. > > Thank goodness the business world is going back to listening > to what Tom's last point was. "... it'll save them money > because development time is cut drastically." > > THAT should be the #1 point that each of us tries to make > when asked about the tool. Yes for goodness sake say the > name, talk about it being around for 8 years, talk about this > wonderful community that we belong to but emphasize "Save > money, better return on investment, etc." > > Spread the word! > > Steve Smith > > Oakbridge Information Solutions > Office: (519) 624-4388 > GTA: (416) 606-3885 > Fax: (519) 624-3353 > Cell: (416) 606-3885 > Email: [EMAIL PROTECTED] > Web: http://www.oakbridge.ca > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Ferguson > > Sent: January 10, 2003 10:34 AM > > To: Multiple recipients of list witango-talk > > Subject: RE: Witango-Talk: What to call it > > > > > > I get these kind of questions from clients also... mostly from > > clients who what me to understand how knowledgeable they > are. Usually > > all they know are > > a few buzzwords. > > > > I'm always puzzled why they are concerned about which tools > I use, as > > long as I accomplish their goals, especially when I'm hosting their > > site and they don't have to worry about purchasing the Server > > component. > > > > Due to its domination of the marketplace, I usually tell > people that > > Tango > > (Witango) is like ColdFusion only better, and it'll save them > > money because > > development time is cut drastically. I've never had anyone > balk at that. > > > > Just my $.02 > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Web Dude > > > Sent: Friday, January 10, 2003 9:27 AM > > > To: Multiple recipients of list witango-talk > > > Subject: Re: Witango-Talk: What to call it > > > > > > > > > Until Witango can get an appreciable market share, I will use > > > "buzzwords" as best I can to land the client. > Unfortunately, I get > > > too many blank stares when I even mention the product. I have > > > clients that I have had for 8 years that now know exactly what > > > Witango is and does only because I educate them on it. I > think the > > > best way to educate a new market is to use Witango itself > in their > > > projects. Once the client is landed, the speed at which > things can > > > be accomplished makes the product sell itself. > > > > > > If you don't get the project, you don't use the product. If you > > > don't use the product, nobody knows what it can do. Sad, > I know, but > > > true. > > > > > > >I agree with John but I say to customers I use and XML > > generating engine > > > >call WiTango which writes its code in XML. This seems to > give them > > > >a buzzword they understand as well as a new word they > have trouble > > > saying to > > > >chew on latter. > > > > > > > >Dan > > > >-- > > > >Dan Stein > > > >Digital Software Solutions > > > >799 Evergreen Circle > > > >Telford PA 18969 > > > >Land: 215-799-0192 > > > >Mobile: 610-256-2843 > > > >Fax 413-410-9682 > > > >FMP, WiTango, EDI,SQL 2000 > > > >[EMAIL PROTECTED] > > > >www.dss-db.com > > > > > > > > > > > >> From: John McGowan <[EMAIL PROTECTED]> > > > >> Reply-To: [EMAIL PROTECTED] > > > >> Date: Fri, 10 Jan 2003 08:25:15 -0600 > > > >> To: Multiple recipients of list witango-talk > > > <[EMAIL PROTECTED]> > > > >> Subject: Re: Witango-Talk: What to call it > > > >> > > > >> Dude, > > > >> > > > >> I believe the term they're all throwing around is "XML > > > Execution Engine" > > > >> > > > >> Personally I think the term sucks. "ASCII Execution > > Engine" would be > > > >> just as descriptive. These types of deceptive tactics will > > only slow > > > >> the growth and popularity of Witango. People need to know > > what we're > > > >> using, *and why* so they tell all their friends about it. > > > >> > > > >> I would never use that term, because I'd feel silly if it > > > made it's way > > > >> to someone who knows what they're talking about, someone who > > > understands > > > >> how proprietary Witango really is. The usage of XML in the > > saved file > > > >> format is no more usefull than the fact that it's in ASCII. > > > Especially > > > >> when you consider the changes that With made to the license > > agreement. > > > >> I can't find a copy of the agreement right now, but I'm > > pretty sure it > > > >> states that you aren't allowed to use the XML > generated by the > > > >> dev studio for anything but running on the app server, or > > editing with the > > > >> dev studio. Which makes using things like JT a violation of > > > the license > > > >> agreement. So, ASCII, Binary, XML, Hindu, It really doesn't > > > >> matter what format the taf and tcf files are saved in. > > > >> > > > >> The only good thing about the file format is that you can > > > open it up in > > > >> notepad to fix a problem when the dev studio decides to > > corrupt it for > > > >> you... I'd better check the license agreement about using > > that third > > > >> party tool with the source code though. ;) > > > >> > > > >> /John > > > >> > > > >> P.S. I'm not trying to start any kind of flame war here... > > > Those of you > > > >> that met me at the developers conference already know how I > > feel about > > > >> this issue. I already know I'm alone on this, and > don't need to > > > >> be reminded... > > > >> > > > >> > > > >> Web Dude wrote: > > > >> > > > >>> I saw this somewhere on the list before but can't seem to > > > find it now. > > > >>> > > > >>> I have a perspective client I have been trying to > land for the > > > >>> last month. It is looking good, but they are asking > for a list > > > >>> of development tools that will be used in the project. I am > > worried that > > > >>> stating I use Witango, will give me the blank stare I have > > seen from > > > >>> other perpective clients I have tried to woo. > > > >>> > > > >>> Someone on the list in the past came up with an > excellent short > > > >>> explanation of what Witango is or does using the word > XML which > > > >>> is definitely a buzzword these days. > > > >>> > > > >>> I need some good examples of what to tell this client so I > > can have a > > > >>> good shot at the deal. Any ideas???? > > > >>> > > > >>> Thanks! > > > >> > > > >> > > > >> > > > > ____________________________________________________________________ > > > ____ > > > >> TO UNSUBSCRIBE: send a plain text/US ASCII email to > > > [EMAIL PROTECTED] > > > >> with unsubscribe witango-talk in the > message body > > > >> > > > > > > > > > > >_____________________________________________________________________ > > >___ > > > >TO UNSUBSCRIBE: send a plain text/US ASCII email to > > [EMAIL PROTECTED] > > > > with unsubscribe witango-talk in the > message body > > > > > > > > > -- > > > > ____________________________________________________________________ > > > ____ > > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] > > > with unsubscribe witango-talk in the message body > > > > > ______________________________________________________________________ > > __ > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] > > with unsubscribe witango-talk in the message body > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
