Re:Why I haven't jumped ship from Common Lisp to Racket just...
by stonemetal on Tuesday August 22, 2017 @10:10PM
(#15078005)
It isn't in DrRacket by default but it is a common enough requested feature that they keep an example of how to add it in the documentation.
https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.htm...
Re:Why I haven't jumped ship from Common Lisp to Racket just...
by mjmein on Tuesday August 22, 2017 @10:21PM
(#15078053)
Thanks. Do you know if it works with the module system - for example, if I edit function definition in a module, and then send that module definition to the REPL, would any code using that module start using the new definition?
Re:Why I haven't jumped ship from Common Lisp to Racket just...
by bad_login on Wednesday August 23, 2017 @07:52AM
(#15080661)
It works in geiser-mode, i don't know if it works with drracket or racket-mode.
http://docs.racket-lang.org/guide/eval.html?q=namespace#%28p...
Re:Why I haven't jumped ship from Common Lisp to Racket just...
by sillysaurus3 on Tuesday August 22, 2017 @10:18PM
(#15078035)
I'm surprised no one has mentioned geiser. It sounds like exactly what you want for racket. http://nongnu.org/geiser/geiser_3.html
Re:Why I haven't jumped ship from Common Lisp to Racket just...
by pera on Tuesday August 22, 2017 @11:18PM
(#15078267)
There is also racket-mode (available on MELPA): https://github.com/greghendershott/racket-mode
Re:Why I haven't jumped ship from Common Lisp to Racket just...
by peatmoss on Wednesday August 23, 2017 @07:41AM
(#15080591)
This is what I use. I find it quite comfortable / very easy to get going.
Re:Why I haven't jumped ship from Common Lisp to Racket just...
by ebzzry on Wednesday August 23, 2017 @11:23PM
(#15087375)
Geiser is fine. However, we can’t compare it with SLIME. The integration of the latter is much better.
Re:Why I haven't jumped ship from Common Lisp to Racket just...
by baldfat on Wednesday August 23, 2017 @07:19AM
(#15080457)
I use Visual Studio Code for Racket.
https://marketplace.visualstudio.com/items?itemName=karyfoun...
Before that I would use VIM with a tiled window manager that worked really well.
My workflow is generally to build up state, and then experiment with functions on that state until I get the correct output.
This workflow is very natural in Clojure, Common Lisp and even Python (with IPython and autoreload).
However, in Racket you have to restart everything on every change. This works ok for smaller applications, but if for example, your state is a large dataset that you pull from a remote database, it becomes a little more difficult.
There are possibly workarounds, and I'm not saying that Racket is bad because of this. There are definite advantages to this approach, mainly for keeping everything simple and predictable. However, this was a roadblock for me, and the main reason why I didn't spend more time working on it.
I also miss the ability to make changes to code, refresh the browser and instantly see the changes (instead of having to restart the server after each change).
Here's a good discussion (in my opinion) of what makes a good REPL for interactive development: http://vvvvalvalval.github.io/posts/what-makes-a-good-repl.h...