Comments on: Dear God, Why Lisp? http://blog.finiteimprobability.com/2008/04/03/dear-god-why-lisp/ Just programming and math, no spontaneously jumping undergarments Thu, 19 Nov 2009 10:30:32 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: felzix http://blog.finiteimprobability.com/2008/04/03/dear-god-why-lisp/comment-page-1/#comment-22 felzix Thu, 02 Apr 2009 21:32:13 +0000 http://blog.finiteimprobability.com/?p=30#comment-22 <p>Nice article. The title certainly appeals to me because I prefer lisp (specifically clojure atm) over all other languages and get some grief for that.</p> <p>Though, clojure isn't actually interpreted. It gets compiled as you go so it acts like an interpreted language as far as not requiring module-wide recompilation after every change. In effect, it's just faster :).</p> Nice article. The title certainly appeals to me because I prefer lisp (specifically clojure atm) over all other languages and get some grief for that.

Though, clojure isn’t actually interpreted. It gets compiled as you go so it acts like an interpreted language as far as not requiring module-wide recompilation after every change. In effect, it’s just faster :) .

]]> By: adam http://blog.finiteimprobability.com/2008/04/03/dear-god-why-lisp/comment-page-1/#comment-13 adam Wed, 23 Apr 2008 15:06:12 +0000 http://blog.finiteimprobability.com/?p=30#comment-13 <p>Right now I have as much of it running in Lisp as I can, including the render loop. If it becomes an issue I can always rewrite that part of it, but for now it is nice to have access to the render loop at runtime if I discover I want to see something for diagnostics. I don't plan on having any really fancy graphics, so taking a hit on execution speed is worth it in this case since I have a bit to spare right now.</p> Right now I have as much of it running in Lisp as I can, including the render loop. If it becomes an issue I can always rewrite that part of it, but for now it is nice to have access to the render loop at runtime if I discover I want to see something for diagnostics. I don’t plan on having any really fancy graphics, so taking a hit on execution speed is worth it in this case since I have a bit to spare right now.

]]> By: No parity between languages « The Parity Bit http://blog.finiteimprobability.com/2008/04/03/dear-god-why-lisp/comment-page-1/#comment-12 No parity between languages « The Parity Bit Sat, 19 Apr 2008 05:01:05 +0000 http://blog.finiteimprobability.com/?p=30#comment-12 <p>[...] up. Clearly this allows for swift bug fixes in the game and AI logic portion of the game. This blog entry about using a Lisp variant for game development highlights why this is a good thing. Now I want to [...]</p> [...] up. Clearly this allows for swift bug fixes in the game and AI logic portion of the game. This blog entry about using a Lisp variant for game development highlights why this is a good thing. Now I want to [...]

]]> By: John Glover http://blog.finiteimprobability.com/2008/04/03/dear-god-why-lisp/comment-page-1/#comment-11 John Glover Thu, 17 Apr 2008 06:15:59 +0000 http://blog.finiteimprobability.com/?p=30#comment-11 <p>Where are you drawing the line between scripting and Java? Some of your examples seem to point to the rendering loop being called from the scripting engine side rather than the other way around.</p> Where are you drawing the line between scripting and Java? Some of your examples seem to point to the rendering loop being called from the scripting engine side rather than the other way around.

]]>