[willwhitney]

Thanks for the support!

I've been thinking a lot about what makes for a good development experience, and how to properly "factorize" an IDE to provide a consistent experience across different languages. The monolithic IDE experience can be great (once you get it set up) if all your work is in a single language. But for people like me, having a confusingly different development environment for each project is a nightmare.

This is a tiny step toward the dream of having a consistent core editor but with powerful tools for each language that allow introspection into the state of the running machine.

[wferrell]

Will -- Nice work! Been hoping for something like this and an excuse to use Atom

[willwhitney]

Thanks Bill!

Atom has been improving really fast - it's my editor of choice now.

[azeirah]

"Nice work Will", "Thanks Bill"!

[stuaxo]

This is great, I've been thinking in a similar about something like this for 'visual debugging', for a livecoding tool.

It would be great if this could recognise some common image formats in memory (cairo surfaces, PIL) and visualise those on mouseover.

Possibly similar for arrays - be able to visualise it as a wave or even playback as audio.

Is there any chance of factoring out the support for the popouts? - It would be great if this could appear in other editors.

[willwhitney]

I'd love to do live variable inspection (like the Chrome Dev Tools) — it's something I'm thinking about for the future.

There's a (nascent) project called `jmp` (for Jupyter Messaging Protocol) that implements kernel communication in JS: https://github.com/n-riesco/jmp. I'll probably contribute to that and factor out my kernel communication.

[lambdaops]

I'm starting up a way to do this with an Electron app (the base of Atom), called Jupyter side car. It's not ready yet, but will share some of the same components. All this is pretty exciting for the Jupyter project.