A very important programming principle is that of separation of concerns. A class should have one clearly defined responsibility. When this is violated problems arise, for instance in the STL.

Most web-browsers today come with EcmaScript ( ie. JavaScript) built-in. Did you know another very powerful language came with Internet Explorer and Firefox?

I just wrote a small open-source JavaScript tokenizer that outputs XML. Here is why you might be interested.

I frequently encounter open-source code which reimplements code which exists elsewhere (and usually does so badly). When everyone is busy reinventing the wheel, no one has the time to build a cart.

More and more programmers and researchers have been suggesting heresies along the lines of "programmers should only work with a view of source code, not the source itself".

The Lua programming language is an extension programming language, which holds special interest to me and anyone who is implementing any kind of interpreter.

I want Heron control structures to be defined as macros. It should be easy for a programmer to introduce a do/while loop or a better for statement. One of the principal motivations, is that the programmer should be able to specialize these things for specific types, or meta-types.

The design of Heron is more inspired by the problems faced by library developers than software developers.

I am exploring the possibility of defining macros as patterns and transformation applied to an s-expression representation of the syntax. Maybe this is the path to writing a fully extendible language?

Macros are a frequently overlooked yet tremendously useful language feature. What if we give them a more modern twist?

Closures are extremely useful, no question, but they are hard to implement efficiently. I am considering implementing them in Heron but with auto-destruction semantics.

Guy says: "Essentially, programmers shouldn't have to worry too much about optimizing while they're writing programs. Instead, that optimization can be done by compilers, either ahead of time or on the fly.", but I disagree.

The latest HeronScript does type-casting backwards.

Every once in a while I come up with a good idea for Heron, and then inevitably Vesa Karvonen tells me that it existed in ML since the dawn of time. Maybe this time will be different?

The trend towards microparsing in XML specifications, is killing the spirt of XML.