The code for my startup is in Visual Basic .NET (VB). Before you laugh, it's essentially just a different flavor of syntactic sugar as C#. For my approaches t

The code for my startup is in Visual Basic .NET (VB). Before you laugh, it's essentially just a different flavor of syntactic sugar as C#. For my approaches to writing code, VB is fine. My scripting language is Open Object Rexx, and a version of it, Kexx, is the macro language of my favorite editor, KEdit. I have about 150 scripts in Rexx. I do nearly all my typing into KEdit and have about 150 macros in Kexx. Some fine day I may move to Microsoft's PowerShell -- if they write better documentation, then I will move sooner. If I have some optimization (mathematical programming) to do, then I will use the IBM Optimization Subroutine Library in object files ready for Fortran from the Waterloo Fortran compiler. So, I'll use Waterloo Fortran. For more in programming languages, I still like a lot that is in PL/I, especially the ideas around tasks, memory management, exceptional condition handling, and scope of names -- all of those deeply interact in nice ways. And I'm totally in love with PL/I structures, much more efficient than objects, a little easier to think about, and nearly as powerful. For more, I want more on a programming language that (1)admits some automatic transformations that improve some properties and preserve others, (2) can report on some of what is going on in the code, and (3) helps with documentation. For (3), IMHO the documentation is more important than the code but in programming language design is treated just as meaningless gibberish and an after thought. Yes, Knuth's literate programming was a step forward but that lesson seems to have been forgotten for other languages.