How does racket mode compare to something like SLY/SLIME? I played around a bit with SLY and it has some pretty cool features, such as implementing methods on the fly, which can be nice when working top down and throwing in some abstractions that need to be implemented later. Debugging with stickers was also very cool. (https://joaotavora.github.io/sly/#A-SLY-tour-for-SLIME-users is a nice intro). I normally use racket-mode when working with racket, but it has been quite a while now and I haven’t used anything like this. Reading through the documentation now
I don’t have a feature comparison chart.
As for “stickers”, I’m also interested in ways to “debug” that are in between the extremes of print and rewriting the whole program to be a step-debuggable program.
I’ve been exploring some ideas with a “tracing” package that emits structured logger events. And enhancing the Racket Mode logger view to consume such events and presents them in a tree view.
But it’s still very work-in-progress.
Just a repo for the tracing package, and a branch in the racket-mode repo.
I haven’t worked on this in some weeks; more recently I detoured into ideas for an inter-file and even inter-project database of definitions and uses of them. So that you could do e.g. a multi-file rename.
[A lot of these ideas are fun to explore. Polishing them to where someone would enjoy using them, and I’d enjoy maintaining over years… is a whole other matter. :woozy_face: So it’s not like I’m rushing to “get things into production”. Racket Mode already has a lot of moving parts and surface area, as it stands.]
Anyway on Monday I’ll call a meeting with the Racket Mode marketing communications team and ask them to start preparing a feature comparison chart. :stuck_out_tongue: