Lisp as an Alternative to Java

I think the lesson to learn from Java was that we, developers, were evaluating languages on the wrong parameters. Java is too verbose! (But that can reduce the need for so many comments, and comments can often mislead as software changes. Also, Java 8 was 2014 and it changed the game massively.) Java runs slowly because of the JVM! (But the JVM evolves and improves, giving free upgrades to all Java programs over time. Also, I have a multi-GHZ processor…

The following are taken from: http://news.ycombinator.com/item?id=1803351 ----norvig 449 days ago------ Peter Norvig here. [....] In terms of programming-in-the-large, at Google and elsewhere, I think that language choice is not as important as all the other choices: if you have the right overall architecture, the right team of programmers, the right development process that allows for rapid development with continuous improvement, then many languages will work for you; if you don't have those things you're in…

This article appears on HN on a regular basis, so I thought people might be interested in a bit of historical trivia: the reason this article is called "Lisp as an Alternative to Java" instead of some other language is that it cribbed the title off my original study (http://www.flownet.com/gat/papers/lisp-java.pdf). The reason that article was titled the way it was is that I was working at JPL at the time and there was a software crisis underway. To that point…

Problem is, programming languages don't matter any longer. The constructs we used to call programming languages are pretty much just used to script between libraries now. So, the simplest language with the best libraries wins. Thus Python, which is the modern BASIC.