Pasting some clarification from a different thread into this one...
Neil Van Dyke wrote on 12/26/18 5:09 PM:
BTW, to be clear (since it took me a while to unravel the vague and
changing meanings of Jupyter and IPython the other day)...
What I proposed in another thread here was adding an user interface to
DrRacket that's inspired by Jupyter Notebook and other notebook
metaphors from stats tools.
There's also a different possible Jupyter angle for Racket, in which
Racket is a backend for the Jupyter frontends (in lieu of DrRacket).
I think that approach would also be useful for some people, and Ryan
Culpepper is already tackling that one (and I wanted to let him
publicize it on his schedule).
These two different approaches might interoperate, if the first
approach also saves a Jupyter ".ipynb" file, and then notebooks files
could be moved back and forth between DrRacket and Jupyter, and run in
both.
These are two very different "Jupyter-related/inspired" things being
talked about, both have merit and uses the other does not, and ideally
both would be done.
I don't want to get into the incomplete list of pros&cons I've thought
of so far about each approach, but I think probably people can agree
that a notebook interface in DrRacket (with all its tools, and its GUI
app properties) is very different than getting Racket backend in a
Jupyter Notebook Web browser interface.
The two approaches overlap for unusual use cases like "I just want to
make a screenshot of *a* notebook interface, and I don't care what
features it has, nor how it works for different people's workflows". I
think they'd each have very different strengths and shortcomings, for
many/most real-world use cases.
(Not mentioning the IPython kernel backend approach was a glaring
omission from my initial post, but I was consciously trying to avoid
confusion, or stepping on Ryan's toes, if he wasn't ready to publicize
his work like I think it deserves. I should've known that many helpful
eagle-eyed people would mention it if I didn't. Maybe I shouldn't have
referenced the current popularity of Jupyter Notebook at all, picked a
likely-familiar older math package notebook metaphor to reference, and
emphasized the desirability of keeping the DrRacket features, to preempt
off-message Jupyter mentions or prime an objection handler for them.
I'm a much better engineer/scientist than I am a marketer, and I'd much
rather work through this kind of system problem myself than try to
convince others to do so, so please be patient. :)
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
