libera/#clim - IRC Chatlog
Search
7:14:26
lukego
I'm making a mistake in doing two things at once: porting the Emacs module from SLIME to SLY and also redesigning the UI. I should do these sequentially instead. The age old temptation to make functional changes while porting/refactoring.
7:15:07
lukego
(but I think there's a lot of potential in this idea of making CLIM presentations of Lisp objects pervasively available in Emacs and having an EMACS-VIEW for CLIM where these can be hooked in.)
7:16:33
lukego
selwynning: So I don't think there should actually be a very big diff initial diff between what I'm hacking and your base branch, not necessarily any changes at all to the MCCLIM-EMACS code. But it will be a multi-step process to get the client side compatible with SLIME+SLY/SWANK+SLYNK at the same time.
9:11:24
lukego
Oh well, my intentions were pure, but the straight port seems like a hassle because SLY and SLIME have different mechanisms for the way a CLIM presentation would find its way to the appropriate REPL. I don't really want to spend time working that out when I could try the New Shiny Approach of having the Emacs side make on-demand requests for the CLIM/SVG representation of various objects that it can reference.
9:18:20
splittist
What is the attraction of Sly over Slime? Folks sometimes say 'stickers!' like it should mean something. It could be I am too dim to grasp the benefits.
9:18:36
jackdaniel
beach: that is the same issue I had in August last year - apparently I had stale version of quicklisp on this computer. sorry for the noise.
9:19:24
lukego
I don't know the answer but it seems like people are using both. Myself I wanted to try out the fancy new Emacs completion frameworks and at the bottom of that rabbit hole it seems like I found incompatibilities with SLIME. So I tried SLY and it Just Worked and so I stuck there.
9:21:48
lukego
I could easily move back to SLIME, I'm not using any of those new fangled completion features anyway, but my vague impression is that supporting both would be good e.g. I saw Xach mention that he uses SLY.
9:23:16
lukego
(If I switched back to SLIME then I'd have to confront the fact that I have wasted quite some hours of toil this week on mucking around with SLY.)
9:28:24
lukego
oh well I'll indulge the sunk cost fallacy until this afternoon and then at least have more data to decide how badly I am wasting my time.
9:29:30
jackdaniel
if my private amusement can weigh on the decision - I'm presonally using slime so it would be nice to have it working in slime
9:31:29
lukego
The existing SLIME-based implementation should keep working just fine. This new SLY-based one may or may not work. If they both work then we can talk about which is better to double down on and make portable.
9:32:47
lukego
(I'm sandboxing all the SLY-specific code into separate files and being conscious of potential compatibility problems. So in principle this could should be easier to add SLIME compatibility too. I'd never looked at SLY when starting the original code.)