[Asterisk-Users] New IAX software phone (for WIndows platform)

[Jon Pounder]

At 12:11 PM 11/3/2003, you wrote:
> > And Visual Basic? Please.
>
>What precisely is the problem with it?  Or are you just a language nazi?  I
>don't like VB any more than you do but if the thing works, who cares what
>it was written in.  Nobody's asking me to maintain it.

I was willing to give vb a chance at one time, but won't touch it any more.

Speaking from firsthand experience here is what led to the eventual 
scrapping of a commercial product written in VB and a vow we will never use 
it again corporately.

1) 95 series / nt series stuff just behaved differently and no amount of 
property settings or traps changed that.

2) third party components are mostly supplied without source code. Vendors 
come and go like the wind so if you depend on something and it turns out to 
have a bug, often the only fix is a redo of the code. Alternatively you can 
write your own, but you pretty much have to do it with c to get the power 
to do what you need otherwise you would have just implemented in vb to 
start with.

3) There were many many bugs in the runtime libs - this may have changed in 
later versions (we tried 3, 4, and 5 with our code, which fixed some bugs 
and introduced new ones.) We finally just gave up on it since the customers 
using it were having constant issues we could not fix without replacing 
whole sections of VB with c code.

4) components changed behaviour with new releases of the "compiler", and 
needed code fixes to accomdate, so trying later versions was somewhat of a 
one way street.

5) The RAD of visual c and its templating is very close to that in vb, but 
you get the component sources, and can fix them if need be.

6) if you need special pieces you are interfacing c to c which is much simpler.
(remember vb uses a pascal style strings and C is an SZ - extra overhead 
and hair pulling to interface, especially when vb has several variants on 
pascal style length storage)

you have to end up asking yourself, is it still vb after I replace all the 
parts with c to get it to do what I want ? if the answer is more than 50%, 
why start with vb in the first place ?




>Andrew
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users