Comments below... -- Alex Kac, CEO/Developer
Innovation in Personal and Business Information Management. http://www.pocketinformant.com/ zoomzoom > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Rick Sanders > Sent: Thursday, August 01, 2002 9:06 PM > To: Multiple recipients of list witango-talk > Subject: Re: Witango-Talk: Witangov5 ?? Vaporware? > > > Alex, > > As one of the people on this list who have been developing > with WiTango and before "Tango", I can empathyze with your situation. > > We looked at .NET for 2 weeks and never entertained the idea > again. Basically, it's the cross-platform abilities and java > bean integration that we need. Most fortune 500 + companies > have Solaris as their web server platform. As well, we were > extremely disappointed with .NET's limitations with creating > web applications for wireless handheld devices. This is Actually, .NET includes a wonderful mobile toolset for creating mobile apps. You can create one app that without work on your part will work on a Pocket PC, WAP phone, or Palm. I know - I've done it. HOWEVER, it's the whole cross-platform issue which is why I've come out of my ASP.NET shell and come back to look at WiTango. > crucial for us since the web is heading in the direction of > wireless communications with the launch of the bluetooth > chip, and 80kbps upload and download from a wireless device. > Put WiTango into the equation, and we've yet to find a better > and faster development platform for wireless web applications. > > All I can say is that at least With isn't making empty > promises like Everyware and Pervasive. There were so many > press releses and release dates for Tango 2000 it wasn't > funny. Finally, Tango 2000 was released 4 months later than > originally planned, and not with all the features that were > in the press release. E.g: The builders were supposed to have > been completely re-designed and do more complex building than > Tango 3. What we got was the exact same builders, with some > enhancements. Very very very very very VERY true. Let me say this - the engineers at PVSW's Tango unit was exemplerary. The marketing folks were good too - but very misguided. Julie Reed was awesome. Andre and others rocked. But - they never were given good instructions on what to do. They spent something like 6 MONTHS writing papers and designing non-usable proto-types of Tango 5. OK, design is great. Its necessary. But 6 months of no coding? Ridiculous. > Basically, I would rather With Enterprises says nothing at > all, than make promises they can't keep, following the same > path as Everyware and Pervasive. With Enterprises bought > Tango to not only make the software better, but also the name > and business practices as well. This way, when With > Enterprises does make their announcements, you can take what > they're saying to the bank. I don't think we're looking for promises. I don't want them to promise. Here's the thing that started all this: 1) From my intepretation of the website, we would know all about WiTango 5 at MacWorld. Great. During and after Macworld - NOTHING. Not one peep. Not even a change to their website. Nada. Zilch. Zero. I hear they've had a private beta going for a little bit. You'd think that once you hit beta, you can talk about SOME of the features? 2) OK after WiTango 5 is released - what's their next goal? Is it WiTango 6? Or fix the IDEs? Is it j2ee server with an awesome IDE? Is it j2ee as an afterthought with a good server? 3) I know Phil likes Macs. Great. So did Greg Hemstreet. But the Greg focused all development on Windows. But Phil isn't all of With. He may be most of it (I really don't know). But even so, Greg H - somebody I was friends with - liked Macs, but focused development on Windows. I'd just like to hear what the Mac plans are as well. I think every adult knows the difference between - PLANS/GOALS and PROMISED FEATURES. ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
