I always felt Slava Pestov's (now abandoned) blog on Factor's development was a good view into language design: http://factor-language.blogspot.com/
He and Andy Wingo (http://wingolog.org) both write very well on language issues though they may skew towards implementation concerns over design concerns.
Hi, Patrick! Sprocketnes has been helpful reading as I've worked on my own emulator. Ian Piumarta's lib6502 uses plain C macros. It's even almost as short as cl-6502...though I don't think it's quite as readable. ;)
Keep up the great work on Rust, been waiting on the gc/scheduler stuff to shake out a little bit. Looking forward to 0.8!
Basically, you write markdown comments in the code and there is a Makefile that uses awk and sed to grab them out, cat some things together and pass it to an awesome LaTeX stylesheet written by Pete Kazmier. See: https://github.com/redline6561/cl-6502/tree/master/src/doc and the Makefile in the parent directory.
Me too! Common Lisp actually was intended for system programming historically, back from when Lisp Machines had a shot at ruling the world. Consequently, there is quite nice support for low-level programming.
Ha. The optional dynamic backend got taken out during a rewrite in August but it was never very interesting. The new plugin and theme support is much more interesting. ;)
That suggests to me that concerns over thread safety that are taken into account in the Java implementation, say of the core data structures, STM, etc, are not taken into account in the std. lib. of ClojureScript. That would make it unlikely for this code to be a useful origin or starting point for, say, an LLVM backend.
Rich is a very clever fellow and makes fascinating trade offs between pragmatism and idealism in his language design. He continues to build languages quite tied to some existing runtimes which embrace their advantages and drawbacks. Consequentially, it will be very important to keep the rationale in mind while evaluating the real impact of ClojureScript. https://github.com/clojure/clojurescript/wiki/Rationale As neat as it would be to see, it will be a long time before an x86 or ARM backend emerges.
As far as I know, the G1 Garbage Collector in the JVM is still the top of the crop of production GCs and even Haskell with GHC7 is still working towards something of similar potency. See http://hackage.haskell.org/trac/ghc/blog/new-gc-preview
Concurrent GCs and other aspects of runtimes geared towards heavy concurrency are insanely hard. Just something to keep in mind.
I'm sorry I didn't get my point across very clearly. Perhaps my writing style is to blame. I often start writing when I "feel it" and figure out what I'm really trying to say as I go then go back and rework as necessary. Too top heavy, I suppose.
Anyway, my point was to celebrate the "heads down, working" nature of a lot of common lispers and to try doing some minor image adjustment. (Common) Lispers don't do terribly much promotion of the language and community or some of its shared values. That often complicates things because folks show up with the wrong idea.
I was hoping this would celebrate where "we" are and maybe clear some things up a little for outsiders. Seems I missed that latter goal. :-/
BKNR-datastore seems really nice but I haven't gotten a chance to play with it yet. Do you know if it supports concurrent writes yet? I know it didn't circa 2008 or so...
Well, the two prominent web frameworks are Weblocks and UCW but their documentation is...wanting. I'm working on a Weblocks tutorial right now but I gave a bit of a survey of the CL web landscape recently: http://redlinernotes.com/blog/?p=1232
Damn shameless self promoters. Anyway, seeing as UCW and Weblocks aren't well documented a lot of people just grab Postmodern or CL-SQL for DB stuff (there are some NoSQL solutions around if that's your fancy), then CL-Who or HTML-Template and Hunchentoot (web server) for the rest.
All the above libraries are easily installable via quicklisp. God bless Xach. And Amazon AWS. :)
That's pretty accurate. I'm still a dumb noob about programming generally but I've been using and lurking in #lisp and the "community at large" for ~2 years now.
The best thing to do for new users is probably to show up on #lisp and solicit recommended libraries for X, I'm afraid. Or google and read extensively, selecting for newer information where possible.
He and Andy Wingo (http://wingolog.org) both write very well on language issues though they may skew towards implementation concerns over design concerns.