There was a time when I was fairly satisfied programming with VBA but once having learned more powerful languages I would not want to go back.
I can remember one of my technical managers coming up with alternative things for VB to mean. For example "I program VB" standing for "I program Very Badly". My favourite alternative acronym was "Vomit Bucket". Part of me wonders if I pick on Visual Basic too much. It served a purpose and introduced a bunch of people to programming who might have otherwise not have done so. Like any language, in the hands of a master, it can be used cleverly. As for me I don't want to go back to building databases in MS Access with VBA. Visual Basic tends to result in messy code and unfortunately the aspect of dumbing down development tends to attract people who are not well grounded in programming (because if they were they would tend to prefer something else anyway). That makes me think. Is it far to say that what you program in can sometimes be less important that the kind of people you end up working with? There are languages I would not normally favour but if I had the right people to work with would be a lot happier about programming in them. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
