I still use it to port stuff to php, and old clients that aren't
worth porting, yet.
No new projects are done in witango, and all big projects are in
porting stages at one level or another.
I PAID well for several copies of a development studio, that has
never worked well, and I still would like to see that rectified. You
have no idea the kind of headaches and time the bugs in the studio
still cost me. The vaporware comment was not off the cuff, or just
mean spirited. It was after a night of no sleep, and some angry
customers.
We have been working on this php port of epx for a long time, and 90%
isdone, but we still had some webservices and some sections of the
site, we left on witango, to meet our deadlines. Also, in this port,
we had added several features to our applications. Some that were too
difficult to do in witango, and easy to do in php, and others just
timing.
We stayed up all night, doing the switchover, and dns changes and all
that. One witango webservice, needed some updates, to allow for a few
new fields. This webservice ingests the event data (not images) that
photographers upload from our software. It is vital, and used
heavily. I left one of my developers with the 3 changes that needed
to be made, at about 2am. I went to bed at close to 5am, and was
woken up at 7am by our support staff and angry customers. They were
getting rejected uploads, and the ones that were working, were
missing data, that involved our new features. I looked in my email,
and my dev had thrown his hands up, and said for some reason, the
witango ws would not work, when he made the changes, and he was up
til 6am trying to sort it out, and finally crashed. He used our
subversion system to roll in the previous version and gave up. So I
looked at the newer version, and it was the !CST bug, again. Now I
have told everyone, and there is a long list of workarounds and
things to watch out for with the 5.5 dev studio, but it was late, and
he forgot about the !CST issue. All he was doing, was adding 3 fields
to an insert, WHY WOULDN'T IT WORK? So I came in and fixed it, in a
few minutes, and got it up, much to his embarassment. No offense to
him, he is a great dev, and a friend, but he was embarassed anyway.
I have several devs, and a lot of code, and this still happens, and I
have to admit, sometimes to me also. Its A MAJOR PITA to have to
check with a text editor after you edit a taf. Sometimes, you forget
to check you are logged into your DSN. And even worse, on mac, for
some unknown reason, you have to constantly reenter your dsn login,
even though saved, because the settings become corrupt or something.
Porting to php was a big task, and I would have rather stayed with my
large investment in witango. But one thing moving has shown me, it
was the right choice. It is true, that there are some nice things in
witango, like building quick search builders and stuff. If I need to
build a quick admin page for a database, I don't know its equal.
However, there is so much more to coding. The time wasted on
workarounds and bugs, FAR exceeds the time savings we used to see
with a neat studio.
On top of that, while witango is trying to get to the point of
working well, and as advertised, other languages, like PHP and .NET,
are just leaping forward by bounds with new features, better
reliability, just leaving witango far behind.
If you could see how I debug web code now, in Zend/PHP studio, it
would make you cry in happiness and disbelief to use it. And all the
tools now at my fingertips, and code out there to start with, is
amazing. And none of the above even deals with the communication and
support issues of Witango Inc.
So I apologize for using the term vaporware sarcastically, but it was
after much frustration.
And I know there will be those that complain that I make negative
comments, but if one thing has been consistent, when I make you
(Phil) frustrated, you respond, and give needed info. So go figure.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Apr 2, 2007, at 7:18 PM, Phil Wade wrote:
I thought you were no longer using Witango?
;)
Phil
On 03/04/2007, at 10:15 AM, Robert Garcia wrote:
I am, and I do have access.
-- Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Apr 2, 2007, at 5:11 PM, Phil Wade wrote:
On 03/04/2007, at 5:23 AM, Robert Garcia wrote:
This is supposed to be fixed in v6 of the dev studio, but both
have become vaporware at this point.
It has nothing to do with vapourware. If Apple every release the
Java SE 1.6 to the general public the beta of the DS will be
available the next day. 7 months after Sun released Java 6 for
every other platform we are still waiting for one from Apple.
That is what is holding the new DS up. If you are an apple
developer connect member and have access to the Developer Preview
6 of the Java SE 1.6 then let me know. I can get you on the new
dev studio beta program.
Regards
Phil
____________________________________________________________________
____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
