Curl-ing, anyone?

Christopher Barber cbarber at curl.com
Mon Oct 29 13:48:10 EST 2001


"Jeff Hinrichs" <jlh at home.com> writes:

> It's closed source proprietary nature, 

True, although we would like to open source part of the technology in the
future.

> it's requirement of installing plug-ins to see content on your browser, 

Yes, but that is not our fault.  Based on this argument, you should only use
technology provided by your OS vendor (e.g. Microsoft).  If you want to
operate under a set of OS'es and browsers you are left with vanilla HTML and
relatively simple JavaScript as your client-side solution.  This leaves you
with really lame GUIs.

Note that Windows XP doesn't even include Java suppport by default, so pretty
soon the same argument could be used to flame that technology as well.

> it's lack of ODBC,  

Yes, we are working on that one.  We do provide XML support and will be
supporting SOAP in the next release, which will be coming out very soon.

> it's skewed vision of web content only or some other pigeon holing 
> "feature" that I have  not brought up.   Like oh yea, to "curl" your 
> site you need to convert all of you html to curl and then have your 
> audience download a plug-in.

No, you don't have to convert your entire site to the Curl language in order
to take advantage of the technology, anymore than you would have to convert
your entire site to Flash or Java in order to use those technologies.

- Christopher




More information about the Python-list mailing list