Hacker News Reader

Comment by pjmlp | Hacker News Reader

I consider Allegro and Lisp Works more useful, as they are closer to the original Lisp Machine/Interlisp-D development experience.

View on HN

Load McCLIM into SBCL. See https://github.com/McCLIM/McCLIM or https://mcclim.common-lisp.dev

It's available also via Quicklisp.

Yeah, I guess it has hardly changed, right?

McCLIM has been changing a real lot, actually, as of late, with many useful changes and bugfixes and applications that use it, such as Clouseau the inspector.

Thanks, I guess it is worth a revisit.

Too bad this GUI framework doesn’t work on the most widespread end user OS.

Please provide a proposal on which UI API a Windows build of McCLIM should target.

This is a serious question. What is the best way of putting lines and text on the screen on a modern version of Windows?

Win32 should suffice.

You put lines with Direct2D and text with DirectWrite.

Why not? Isn't there X11?

Screenshots of interesting apps are here: https://mcclim.common-lisp.dev/excite.html

They should really appear in README.md!

Is Lisp Works compliant CL, such that any CL written in their IDE will work with SBCL too?

Any ANSI Compliant CL will work on all implementations that are ANSI compliant

So in short, yes, except for any third party libraries

Okay cool, I guess my question is how heavily do third party libraries feature in Lisp Works such that you’re then tied to their ecosystem?

For a lot of things there are portability libraries that bridge vendor extensions between implementations. So, in practice, you can use features that aren't part of the ANSI standard (threads, sockets, ffi) without tying yourself to a single implementation. Also, FFI is pretty trivial in most implementations.

Cool! Thanks for your response. So would you suggest Lispworks as a good development environment for new Lisp hobbyists who aren't keen on Emacs?

Reply on news.ycombinator.com