I've developed quite a few languages: (1) Strix, a rule-based language with SNOBOL4-style string pattern matching. (2) ENeMaL, a rule-based expert network man

I've developed quite a few languages: (1) Strix, a rule-based language with SNOBOL4-style string pattern matching. (2) ENeMaL, a rule-based expert network management language. (3) Gossip, an object-oriented Prolog (4) Emblem, a Lisp dialect. I've been using Emblem to develop (5) Full Metal Jacket, a visual dataflow language (http://web.onetel.com/~hibou/fmj/FMJ.html http://web.onetel.com/~hibou/fmj/FMJ.html) There will always be a demand for domain-specific languages. I'd think hard about developing general-purpose languages. There are plenty out there already, and you could contribute towards them instead. If you want to develop a new language for release, it's a good idea to develop several others first for your own use to gain some practice and learn what's involved. Why have I developed Emblem? I wanted something simpler than Common Lisp, but didn't want to rely on third party libraries. It has support for 2d and 3d graphics, statistics, symbolic AI and a few other things. Why have I been developing Full Metal Jacket? I wanted something significantly better than Lisp, with directed graphs as the fundamental data structure, extreme type safety, and the ability to run efficiently on multiple CPUs. It isn't ready for release yet, and I'm taking a break from it at the moment. I'll consider it a success when I start using it in preference to Emblem.