When doing serious development and hitting these issues, the workaround isn't to continue using a broken language. The workaround is to use a different language

When doing serious development and hitting these issues, the workaround isn't to continue using a broken language. The workaround is to use a different language. The first question 'Does this language run on the target system that I need it to?' isn't a yes or no question. Take a look at this example - http://blog.fogcreek.com/the-origin-of-wasabi/ http://blog.fogcreek.com/the-origin-of-wasabi/ A language that compiles to PHP and ASP, what a relief. And for the contemporary result - http://blog.fogcreek.com/killing-off-wasabi-part-1/ http://blog.fogcreek.com/killing-off-wasabi-part-1/ When the platform catches up, then you can go back to mainstream development with a useful language.