Hacker Timesnew | past | comments | ask | show | jobs | submit | andyhd's commentslogin

I'm planning to write a game for Ludum Dare 42 using SBCL and clopengl. I wrote a simple Asteroids game way back with SDL (https://github.com/andyhd/asteroids), but I haven't had much opportunity to use CL since then. I find Lisp is the most enjoyable language to write in, because it has such minimal syntax, but is incredibly flexible.


I was planning to write about my experience writing this, so I'll keep you posted.

It's really not elegant or special code at all, though, just something I used to learn some more about Lisp.


Please do!

Lisp has this reputation within the hacker community, and I'd love to hear some impressions from people who are new to it.


Thanks!


Thanks for your support! I totally agree with you - I put the code up on Github because I figured someone like me might want to improve it or take it in another direction.


I wasn't trying to write it in less than 600 lines, that's just what the OP used for an interesting title, I guess.

It's just a fun project I did to learn a bit of CL. I translated the code from a Python game, so it's not in pure functional style. Now that you mention it, though, I feel like I should try that.


Thanks for the tip. I didn't realize numbers with the same value could be different to eq.


Hi, author here. I am new to Lisp (about 4 months in) and I've been a happy Vim user for many years, so I'm not finding the transition to Emacs very easy. I am trying, though.


I'm a very happy vim user too. Sadly, short of commercial IDEs, developing lisp without slime is like developing Java without eclipse or intellij; it's just an inferior way to interface with the language.

For vim users, the two choices are vim+slimv and emacs+evil. I find evil to be closer to vim than slimv is to a good slime experience, but that can change. Also, if you have any vim plugins that you really depend on then slimv probably edges out evil.

On the other hand I started out several years ago with viper plus a bunch of hand-coded elisp functions to use my most commonly-used vim commands, so we've come a long way.


Weird, it was working when I posted. Fixed now.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: