Programming languages I have stopped using

I do not support the use of these programming languages. Any people that is still choosing any of these programming languages for production code should be considered a bad manager or programmer. Of course, if you buy any software developed using these programming languages you will make a very bad decision.

• Visual Basic, Visual Basic .NET, Visual Basic for Applications and VBScript they have inconsistent syntax like totally insane array creation (Dim age(6) as Integer will create a seven element array). Visual Basic is such a badly designed language that has made a lot of harm to IT. Microsoft should stop adding features to it and just keep maintaining for some years (there is lots of installed base) and encourage costumers to move to C#. All of the Visual Basic projects I have ever seen have been a failure or much worse than a similar project in a decent programming language. You should be moving to Java and JavaScript or C# if you are still in Microsoft world.
  
• Tcl It is slow, not object-oriented and totally dynamic (I prefer static typing). You should be moving to Python if you want a clear scripting language. Tcl problems [Reddit]. 10 problems of Tcl.
  
• MATLAB were indexing is one based, as it is conventional in mathematics, instead of zero based like normal programming languages. You should be moving to SciPy if you need clear syntax and a complete programming language. Take a look at "Bye Matlab, hello Python, thanks Sage" to know a personal history why the migration is worth it.
• Perl. It does not have a cycle detecting garbage collector (so it can leak memory). It is quite difficult to do object-oriented programming. The code written is not easy to maintain with a group of people. You can see Perl5 drawbacks at Lua Versus Perl5 and Why Python?. Switch to Python.
  
• Shell script as I said in a previous post, shell scripting can be handy but it is not worth the trouble and it is not an option for anything but a simple small script.
• I have never programmed in COBOL, but I am happier for not having to. Just compare the same code in C# and in COBOL. COBOL is a dinosaur.
  

I agree with Edsger W. Dijkstra (Why numbering should start at zero) that any one based array programing language is not serious.