Hey Dude, Life is change.
I have to confess, one of the reasons I haven't been as attentive to the List lately (and why I missed that New York Trade Show) is because I'm buried deep in a new project with our company and a Major International Accounting Firm. Although the web-development portion of the project is minor in comparison to the whole - the whole project will likely take 2 years to finish. We tried to sell them Witango - but it was a no go. Instead of getting into a long-drawn-out squabble of the merits, pros and cons of which development environment is better - we said we'd give them whatever they want, rather than risk not getting the job. Now, I'm not saying I've abandoned Witango - just that I've added more options to our capabilities. Life is change - so why is Software Development any different? Why offer your customers just one development environment option? I can say these things about Witango without regret - because the people at With are the same. They see that development trends are a moving target too. That's why they're building their Java Compiler - and have hinted at a .NET compiler. I can now add C# and ASP.NET to my resume - right along side of Witango. >From my point of view as a Witango developer - I'm very excited about my new skills, because I want to build us some 3rd Party add-ons for Witango, such as a "SOAP Web Service Publisher for Witango" :-) And yes, I can add "with experience" that coding in ASP.NET is not nearly as fast as Witango - but I do have more capabilities as a language. So the "extent" of a project is also a driving factor in many IT decisions. There is no one perfect answer - so have some options. With is about to release there Java Compiler - so how many of you are learning Java RIGHT NOW? -- Question to Phil: Any news on that .NET Compiler?????? Sorry Dude, this was probably not the sympathetic reply you were looking for. Cheers.... ----- Original Message ----- From: "Web Dude" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: Friday, January 10, 2003 11:10 AM Subject: Re: Witango-Talk: What to call it > Thanks Scott > > Excellent page. > > I didn't realize I was opening up Pandora's box with this thread. I > can see everyone's point fairly clearly. But the brunt of the > situation with myself and my company is the fact that... yes we have > lost jobs over the type of development used. And yes, I had a major > client of mine spend a year with several (minimum of 3, somtimes 5) > developers that took all the work I did on their site and switched it > to .NET. I bet they spent several hundred thousand dollars doing this > switch. When I asked management why, I was told that the IT > department said Witango was dead; the IT department did not > understand Witango nor were they even willing to learn (they were all > young kids fresh out of school); they couldn't find local developers > that were willing to consult using Witango except for myself; they > spent $25,000 on T4. > > What really ticks me off is the fact that they took my logic on how > the site was layed out and worked it to .NET. The site was a portal > to sell their products through other affiliates. It had 181 > affiliates when I left and probably has a lot more now. All the html > tags, metetags and style sheets were stored in SQL and called from an > affiliate ID. As far as I know, the SQL never changed, just the front > end to access the info. So really it was 181 separate websites with > different fonts, colors, art, buttons, phone numbers, addresses, etc. > > well ... I thought it was nifty :) > > Sorry, I digress... > > Anyway, the facts of the matter for me is that I can understand the > Witangoers beating their drums for the product, heck, I got a big > stick that I bang too. But most of the people I have to convince in > using my services are usually illiterate when it comes to development > and they need some sort of comfort level or I am going to miss out on > the job. Competition is very fierce here (Minneapolis) and 80% of all > developers seem to be using Micr$oft. and if not Micro$oft, Cold > Fusion. So a manager who makes the decisions will ask someone in > their company (usually an IT guy) about Witango and they will get "I > never heard of it" but asked about XML they will be good to go. > > Sorry these are the facts of life for me. > > > > > > >I might be going out on a limb, but maybe this is what you were looking for: > > > >http://xml-extra.net/webpage.xmlx?node=84 > > > > -- > ________________________________________________________________________ > 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
