the JVM. dynamically typed, extensible, interactive programming with functions, emphasis on immutability “Use it anywhere you would use Java” runs on the JVM, designed for the JVM
int balance Account String firstName String lastName String number String ssn int yearStarted Employee String name String code int inventory Product String name String code String address String tel Customer DateTime timestamp String clerk int totalAmount int vatAmount Receipt
work, but as they are held in contempt by all, no Verb is ever permitted to wander about freely. If a Verb is seen in public at all, it must be escorted at all times by a Noun. Of course “escort”, being a Verb itself, is hardly allowed to run around naked; one must procure a VerbEscorter to facilitate the escorting. http://steve-yegge.blogspot.fi/2006/03/ execution-in-kingdom-of-nouns.html
provides you. So whenever a new idea occurs to you, you have to sculpt it or wrap it or smash at it until it becomes a thing, even if it began life as an action, a process, or any other non-”thing” concept. I’ve really come around to what Perl folks were telling me 8 or 9 years ago: “Dude, not everything is an object.” http://steve-yegge.blogspot.fi/2006/03/ execution-in-kingdom-of-nouns.html
going on is not so much that Lisp has a strange syntax as that Lisp has no syntax. You write programs in the parse trees that get generated within the compiler when other languages are parsed. But these parse trees are fully accessible to your programs. You can write programs that manipulate them. In Lisp, these programs are called macros. They are programs that write programs. http://www.paulgraham.com/avg.html
(AbstractLazyInitializer.java:86) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation (AbstractLazyInitializer.java:140) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke (JavassistLazyInitializer.java:190)
are usually broken, and therefore their behavior itself, never mind their performance, is unpredictable. That’s been my experience with manual locking in the hands of mere mortal developers. http://www.azulsystems.com/blog/cliff/ 2008-05-27-clojure-stms-vs-locks
port of Harlequin Common Lisp, flew aboard Deep Space 1, the first mission of NASA’s New Millennium program. Remote agent controlled DS1 for two days in 1999. During that time we were able to debug and fix a race condition that had not shown up during ground testing. Debugging a program on a $100M piece of hardware that is 100 million miles away is an interesting experience. http://www.flownet.com/gat/jpl-lisp.html