Executable code environment

[rjbergerud]

This is probably outside the scope of what this application is trying to accomplish. I have some sort of vague idea of athens meets jupyter notebooks, where you can mix back-linked note-taking and executable cells.

[tangjeff0]

Right now we are focused on research and notetaking, and users do take notes on math, science, and programming. It makes a lot of sense for us to focus on building an executable code. It's pretty easy to do live JS and CLJS in the browser today. For languages like Python, I would have to look closer, but I think we would need WASM and GraalVM, otherwise we would be re-creating aspects of repl.it.

[tomisme]

I'm super excited by the idea of executable code in Athens, I did a tiny demo of using SCI, passing data between blocks and rendering hiccup in Athen's devcards some time ago. Are the devcards still working btw @tangjeff0? This page seems down.

Lots of unanswered questions like, how do I safely expose part of my knowledge graph to a code environment? How might I trust 3rd party code?

I reckon the answers lie in the Principle of Least Authority and things like Capabilities .

[tangjeff0]

@tomisme devcards still compile and open locally, although they are out of date. I'm not sure we publish them to GH pages anymore.