Well, it would be sad to see you go Alex, since you would be a valued developer on this list, particularly with your programming efforts in the PIM area, so I hope that you find enough in the new version to keep you interested. I would have thought that some of the items mentioned in your wish-list were a bit beyond what the "average" developer (if there is such a thing) would be expecting, I would have thought, but they certainly would take the product a long way further than the previous incarnation and would be exciting additions. I do think that even if the product doesn't live up to these expectations initially, the extension of its legendary ease-of-use and new speed and stability, along with the advancements already mentioned (j2ee etc..) must make it worth consideration for the majority of us.
I must say I think that if you went it would be a duller list as well - the number of emails in this thread has got to be a record, and you certainly have made life a little more interesting on the list! cheers Garth At 07:36 30/07/02 -0500, you wrote: >Comments below. > >-- >Alex Kac, CEO/Developer > >Innovation in Personal and Business Information Management >http://www.pocketinformant.com/ > >zoomzoom > > > > From: Robert Garcia <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > Date: Tue, 30 Jul 2002 16:31:12 -0700 > > To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> > > Subject: Re: Witango-Talk: Witangov5 ?? Vaporware? > > > > Several of these questions can be answered without violating any secrecies. > > As a beta tester of v5, I can also answer with some authority. See below. > > > > -- > > > > Robert Garcia > > BigHead Technology > > 2781 N Carlmont Pl > > Simi Valley, CA 93065 > > Phone 805.501.1390 > > Fax 805.522.8557 > > http://www.bighead.net/ > > [EMAIL PROTECTED] > > > > > >> From: Alex Kac <[EMAIL PROTECTED]> > >> Reply-To: [EMAIL PROTECTED] > >> Date: Tue, 30 Jul 2002 17:32:41 -0500 > >> To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> > >> Subject: Re: Witango-Talk: Witangov5 ?? Vaporware? > >> > >> 1) Am I better off using T2k to develop and deploy using JTransit? > > > > Absolutely not. You will receive much better performance and compatibility > > with Witango v5. Jtransit will always have to run on top of a Java layer, > > and a virtual machine, which will always be slower than natively compiled > > code, which Witango v5 is. > >Tango server is not running compiled .taf code. Its a VM just like Java is. >And many JVMs are very optimized. They have many more people to optimize the >code than With does. > > > > >> 2) What does it offer that makes it a T5 release? Is it EXACTLY the > same as > >> Chimera (aka SP2 of T2k)? If it is - then I see no worth in T5. I'll > just go > >> with JTransit or move off to something else entirely. > > > > In my opinion, the biggest change is the threading model. As Phil told > me at > > the conference, one of the biggest secrets at Pervasive was that the > > software was cooperatively threaded. You see, Tango was originally written > > for the classic Mac OS, which is a cooperatively threaded operating system. > >Yes, I know this. I've been running Tango since 1995. Not only that, I have >spent many hours directly with the engineers of Tango up in Toronto while >working at PVSW. I have even worked with some of the Tango source code. In >fact, at one point I spent a week in the Tango Server source code - I know >how it works. > > > Witango v5 is completely rewritten using a preemptive threading model. This > > makes the server faster, and more reliable. If one user is doing some huge > > query on your server, it will not lock every one else out until it is done. > > Once again, in my opinion, this is HUGE. I have tested it, and it makes a > > tremendous difference. If you remember, pervasive used to state that the > > standard server was designed for up to 50 users. And if you benctested T2K > > like I have, you would see why. The performance would die at that level due > > to the threading. > >Yes, I know this. Again, MY point is that this was done 2 years ago. Now >Chimera was worked on - and then stopped for over a year until With bought >Tango. > > > Also, you know all of the bugs that have been a pain in the ass with T2k, > > that have been whined about over and over on this list, many whinings my > > own? Well, much attention is being spent at fixing everyone. I have had my > > own huge list, and it is almost completely checked off. This goes for the > > editor as well. These bugs will be even more worked out when it goes public > > beta in a butthair or two. ;-) > > > >> 3) Does T5 include the java compiler? > > > > I have no information on this, sorry. > > > >The problem with all your answers is that it assumes I'm upgrading from >Tango 2k. Yes, I still run Tango 2k - but none of the .tafs running are >mine. > >I'm coming from ASP.NET now as well as a bit of Java and I am very >interested in know how WiTango 5 compares to them. I am really not all that >interested in knowing the above about the server core because frankly, I >would assume that they are there now. If they aren't, then Tango really >isn't even worthy to be called a server now. 3 years ago, Tango 2k was >awesome. Now, its as good as engineering student's project. So WiTango 5 >needs to offer all that you list above - without bullet points. Those items >should be assumed. The bullet points that would make it interesting are: web >services support, built in "controls" for data ala the ASP Datagrid, built >in data cacheing, session support across servers, session support in a >database, and access to hardcore languages for real down and dirty work at a >more fundamental level. That would bring it to the level of CFMX, j2ee, and >ASP.NET. And all of those cost less than WiTango 4 does now (well, the j2ee >depends). So that's my viewpoint and that's what I'm looking for. > >I will GLADLY go and be on my merry way once I know these things. Frankly, I >expect that I'll be gone before then since at this point from what I have >heard and seen, I don't think ANY of those will be answered positively. > >________________________________________________________________________ >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
