Those are some really good points Scott. PhP though in my opinion isn't as robust of a language, at least on Windows. It needs constant attention, load-balancing isn't available, and it has far too many security holes which makes it easily hackable. If you use PhP, I suggest using on Linux with Apache, that's what it was built for in the first place!
Needless to say, I love Witango and it is by far the best development language for rapid application development. However, looking at Visual Studio 2008, and Dreamweaver CS3, the WiTango editor is light-years behind these development platforms. The integration between code and design layers just isn't there. Typically I would build the application, then plug-in the design with a series of include files, then build any additional WiTango app functionality in the include files. TCF's are great, but is it me or when the TCF's get too large they tend to not function as well, and bog-down the server? I don't have any issues when using cfc's with Cold Fusion. And, I build my CSS in dreamweaver because it's so easy to do. It doesn't make sense today to use 5 programs to develop an application. ASP.NET is a tough language to learn if you are new to it. However, the control you have over the code and options you have for developing are phenomenal. It ties into the operating system extremely well, and you can build web applications that talk to active directory, and even go to the extent of installing a network printer and defining permissions right from a web application without any external components! Building CSS in Visual Studio 2008 is also a breeze. Unforunately, Mac users can't take advantage of Visual Studio, or host ASP.NET applications on a Mac. Cold Fusion is a faster development language, and I would say it's as fast as WiTango if you are familiar with Dreamweaver. Dreamweaver will build the SQL just like WiTango, and integrating it with the design layer is a snap! Cold fusion 8 has alot of new features built-in, like uploading a picture and resizing it on the fly like image magic. If you use flash alot for applications, video and such, then Flex is the ultimate design tool for developing a graphic layer around Cold Fusion. Converting WiTango code to Cold Fusion is fairly easy. I've converted many apps, and they work just as well. Customers are getting smarter and more educated about web programming and database platforms, which makes it increasingly difficult to suggest WiTango as a language. Very few people host it, and have heard of it. I know that Pervasive is a dirty word to alot of you, but they did do alot of marketing and promotion of the product to gain awareness, and they did make the product into XML instead of binary code. Rick Sanders Webenergy Canada: 902-401-7689 USA: 919-799-9076 Canada: www.webenergy.ca USA: www.webenergyusa.com -----Original Message----- From: Scott Cadillac [mailto:[EMAIL PROTECTED] Sent: January-28-08 12:38 PM To: [email protected] Subject: RE: Witango-Talk: Re: is witango alive? Hi Stefan, That's an interesting observation. I did the opposite. I was actually doing ColdFusion prior to starting in Tango, which I found was one of the reason I found Tango so easy to learn. The syntax and tag methodologies are very similar. PHP is not too dissimilar as well I think, given that all three are interpreted languages. I guess the difference with PHP is that additional architecture features have been bolted on to PHP since its original design, and of course many serious developers want to take advantage of that. I think PHP apps can even be compiled now if I'm not mistaken, but maybe I have that wrong? With ASP.NET for example, it's not an interpreted language (classic ASP was), it's compiled. And given that it's integrated with IIS to create a real application server, the underlying architecture that handles the code execution is very different than ColdFusion, Tango or PHP. Java is also in this class of architecture, to a degree. This makes the transition from Tango to ASP.NET much more challenging. I've converted many Tango apps to ASP.NET for myself and other folks, and as long as you know both languages well, the transposing of the code is reasonably painless. I guess the key is, depending on where you're heading, is to learn your new platform first before the conversion, and just don't assume as you start out that it'll be just like Tango. For those not interested in PHP, I would checkout the conversion tool in Witango that compiles to Java. I haven't used it myself, but I bet that would fast track anybody's learning curve to a deeper application architecture very much. When Phil first proposed the Java compiler apparently there was plans for a .NET compiler too, but it never materialized unfortunately. Oh well. Scott, On Monday, January 28, 2008 11:36am, Stefan Gonick <[EMAIL PROTECTED]> said: > Hi Everyone, > > I'm here and continuing to program in Witango for my existing clients. > > I found it very interesting to read how hard it is to convert a > Witango application > to PHP since I don't know PHP. Years ago I learned ColdFusion and converted > a Witango application back then. > > I found it extremely easy to do the conversion. The two languages were very > compatible in how they did things. In fact, mostly all I did was promote the > html result actions into their own pages and substitute equivalent CF > tags for the > Witango ones. Obviously, I had to add the sql query at the top of the page, > but > I even used the View SQL command of the search action to get a head start on > that. It was very quick and easy. > > I later did a CF application from scratch but actually found development to go > faster by using the search and new record builders in the Witango > editor and then > convert the results to CF! Pretty cool. :) Anyway, I just thought > that I would share > my experience of the compatibility between CF and Witango. > > I appreciate this thread. I've been wondering if Witango is alive > lately myself. A major > part of what has been making me wonder about the viability of Witango > is the lack of > news from With. It would be great if they would chip in at some point... > > Best to all, > Stefan > > ===================================================== > Database WebWorks: Dynamic web sites through database integration > http://www.DatabaseWebWorks.com > > ________________________________________________________________________ > 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
