News for hackers. Stuff that matters.
Re:Lisp as an alternative to Java (2000) [pdf] by agumonkey on Sunday October 12, 2014 @05:18PM (#8446635)
I forgot to mention that the main lisp implementations (SBCL) are fast. Compared to languages like these it's a done deal.

Good point about long term maintenance. Ruby and Python aren't that great either, people say static typing is the way to go. Lisps are weird because they allow to hot swap most of the things which makes changing a system easy, but at the same time it leads to spaghetti images.

Re:Lisp as an alternative to Java (2000) [pdf] by _delirium on Sunday October 12, 2014 @05:43PM (#8446703)
My experience is that long-term image-based development isn't really that common in Lisp, maybe outside of some specialized use-cases. You can develop by mutating/saving/reloading an image over an extended period of time, but in practice people mostly develop the "usual" way, with source code that's loaded into a fresh image periodically. The use of image-oriented development then gets limited to prototyping and debugging. Being able to redefine functions/etc. on the fly (even during restarts and the like) is useful while experimenting and debugging. But then the "real" code gets written into a source file, which is reloaded into a fresh image to make sure it works. For modern muti-developer Lisp this is pretty much the only way things are done, since the expectation is that you check Lisp source into svn or git, not images.
Re:Lisp as an alternative to Java (2000) [pdf] by adwf on Sunday October 12, 2014 @06:25PM (#8446799)
That's pretty much exactly how I develop. I rarely type anything directly into the REPL, instead typing into the source file in emacs and then C-c C-c it over to the REPL for me. The advantage is that I get a canonical copy of the entire source code, whilst still having the ability to inspect and hotfix things through the REPL. If I then need to reboot the image or deploy to a new server, the entire source base should be completely stable and consistent.

I often connect to production servers using Slime and fix little things like typos this way - then check the source into Github and have it permanently saved. It removes a lot of the stress of doing a full deployment each time you need to patch something!

Re:Lisp as an alternative to Java (2000) [pdf] by philippeback on Monday October 13, 2014 @03:32AM (#8447813)
Same story with Pharo Smalltalk where we run CI jobs loading things into fresh images.

Code lives in Git as well via GitFileTree.