Certainly I have been interested in the completeness of WO and have thought to move my work to WO, but I think that the coming version of WiTango will go a long way to soothing my itches, and give me enough reasons to stay loyal to WiTango.
I think that once you get used to something, unless there are significant drawbacks (such as lack of cross-platform in Alex's case, (previous) lack of Java deployment etc.) with your current tools you stick with what you have invested the most time with. There are going to have to be compelling reasons for other developers to move away from ASP.NET and WO to come to WiTango (I know, there are some good reasons now but...) but I think as long as the focus from WI on product development, and keeping the bugs to a minimum, remains, by version 5.5 or 6 we should have the hands-down best IDE and deployment setup on the market (unless someone else comes up with something blindingly amazing). I agree with Scott when he says that we need to make a decision to get behind the product and change it for the better (or best). And in doing so, it'll become an amazing testimony to the efforts of a small development company and a incredibly supportive developer community. Garth At 10:33 1/08/02 -0500, you wrote: >I sincerely hope so. That's been a big part of my entire conversation >here. BTW, you know the last time I posted so many times in a >Tango-Talk??? It was 4 months before I was hired at PVSW to work on Tango >projects there - right when Tango was bought out by PVSW and they screwed >up the mailing list. > >I know quite a few of former Tango developers who now are WO developers - >and I hear a bit opposite. Its not as easy as Tango, no - but I haven't >heard from them the kind of issues you describe. > >-- >Alex Kac, CEO/Developer > >Innovation in Personal and Business Information Management. ><http://www.pocketinformant.com/>http://www.pocketinformant.com/ > >zoomzoom >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]] On Behalf Of Robert Garcia >Sent: Thursday, August 01, 2002 10:09 PM >To: Multiple recipients of list witango-talk >Subject: Witango-Talk: Comparing WO to Witango > >Many moons ago, I started a thread labeled Sad Day , where many of us >announced our intention to move away from Witango. My intention was to go >to WO 5. > >I have owned and kept up to date a full deployment version of WO since >4.0. I have played with it at times, but when I started Sad Day , I made a >commitment to completely tackling WO 5 and moving all of my code over. I m >an all or nothing kind of guy. Apart from my Witango programming >experience, I am a fairly experienced Java programmer, and until I found >RealBasic, I spent a lot of time using it. I spent a whole month with WO >5. 12 hours a day, full boar. Yes, I could do anything I could do in >tango, but at a huge price. The IDE constrainsts made every thing take 3 >times as long or more. And I was mistaken when I thought WO was less >buggy. As I dug in, hit the lists and read the articles, it seemed that >the learning curve everyone talks about with WO is two fold, first you >have to learn the IDE, then you have to learn the workarounds. It had its >atractions though. I would love to see tango work on its builders to get >something more like WO s direct to web feature. > >I have also worked in JSP and ColdFusion, and dabbled in ASP. But nothing >compares to the flexibility and simple logic of the tango editor. With >tafs, tmls, tcfs, beans, com objects, you have a wealth of tools to help >you accomplish the amazing. But you can also throw an quick app together >in a few hours. And isn t that the point? Get it done quickly, get paid, >and move on to your next project. Of course, not sacrificing quality. And >that is where v5 comes in. It brings the quality and performance back to >the greatest webapp IDE around. > >Of course, this is all my opinion. > >-- > >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] ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
