Python vs. VB

[Tom Culliton]

I've got a friend here who claims that you really can't do that much
which VB without programming by purchase order.  That is to say
sitting down with a widget catalog and nickel and diming yourself to
death.  (I'll CC Dave and see if he wants to toss his two cents worth
in.)

I've seen (but fortunately never had to deal with or maintain) way too
much very bad VB code.  Even good programmers have a hard time writing
clean VB code and bad programmers create unspeakable horrors.

This versus Python where it's hard to write really bad unmaintainable
code, and you can easily write stuff thats still a pure delight to go
back to weeks or months later.

In article <7hq29e$kgs$1 at Starbase.NeoSoft.COM>,
Cameron Laird <claird at Starbase.NeoSoft.COM> wrote:
>In article <37407bc5.343558265 at news.esinet.net>,
>Roy Stephan <roystephan at yahoo.com> wrote:
>>My company is mostly a VB shop.  Web Development has gotten away with
>>Perl in a corner but we are now being urged to move to ASP.  I am
>>pushing for PerlScript interfacing heavily with COM.  
>>
>>I would like the COM objects to be implimented in Python rather than
>>VB.  
>>
>>I was wondering if people on this list could provide me with some
>>amunition against the managment onslaught that will surely ensue in
>>favour of all things Microsoft.  
>>
>>Are there any existing comparisons/benchmarks?  Is there anyone out
>>there who has won a similar battle?
>			.
>			.
>			.
>Yes, but most interesting are the pertinent ones.
>What matters to your decision-makers beside the
>Microsoft label--reliability?  Time-to-develop?
>Object orientation?  Performance?  If they are
>truly committed to Microsoft in an irreversible
>way, there's perhaps little profit in fighting an
>unwinnable battle.  If, on the other hand, there's
>some existing issue with VB, perhaps we can
>address it specifically and concretely.