Is Google Docs integration with iPython Notebooks a good idea?

Google Docs should integrate iPython Notebooks, period. It would be so great to run python inside a Google Doc / Notebook. It would make Google Docs the Lab Notebook of many scientists.

Ok, but first, what are iPython Notebooks? A Notebook is basically a web-based user interface for authoring and running Python code and rich text. It saves everything in JSON format and is therefor very portable and useful for experimenting, prototyping, data exploration, and teaching. It is very useful because you don’t have to rerun your entire python script, or if you’re in a python repl you don’t have to retype everything. You just change what you need in the cell you want and rerun that cell. See an example of the output of one iPython Notebook.

Why Google Docs should integrate iPython Notebooks? Google is one of the big boys of python. It also provides appengine that allows you to run your python apps on their servers. So I’d say that 90% of the infrastructure is already in place for Google Docs to support iPython Notebooks. Obviously Google doesn’t want to give you access to some low level parts of Python but they could implement Notebooks in with the same kind of sandbox they have in Appengine.

Now imagine that google can go even further and integrate iPython Notebooks with their collaborative Google Docs environment in a way that many contributors could be working on the same document and in the case of Notebooks we are talking about running code in the same document, simultaneously. Imagine several users sharing a python session within a Google document. Obviously sandboxed and secured and all that. Imagine remotely working in this way with partners across the globe.

Imagine teaching programming on a ancient Blackboard Notebook while your students experimented live and you’d be monitoring and helping them in the same document? The results of their actions would be immediately available and they could see what worked and what didn’t. How great would that be?

Also imagine the potential of using google infrastructure to run some pretty tough simulations. All from within a Google document and with results available immediately at the right place in the document you’re writing. In the end you’d just be exporting the document to a PDF and sending it to the journal… :)

Google Docs + iPython Notebooks could become a revolution in the way you write documents and run software. They would stop being two separate activities and become mixed in a way that would become natural. (obviously there are some attempts to do this in other softwares: for example R + Sweave or R + knitr, or Mathematica Notebooks, but none has the potential to spread as a combination Google Docs + iPython Notebooks).

With all this potential, I believe that if Google integrates iPython Notebooks as a native supported format in Google Docs, they will get a lot of love from my mom many scientist all over the world. Go ahead Google, just do it!

iPython Notebooks

Google Docs

Notebook Example for VAT simulation in portuguese

Títulos do Google Docs

Costumo utilizar o Google Docs com alguma regularidade, nomeadamente quando estou a tomar notas nas aulas de mestrado e não tenho o portátil comigo.

Verifico que é profundamente irritante quando, depois de se ter guardado o documento, se alterar a primeira linha do documento (que dá o título ao mesmo) e ao re-gravar, o Google Docs em vez de alterar o documento gravado, decide criar um documento novo.

Como eu tenho o hábito de ir alterando os títulos a cada duas frases novas acabo por ter meia dúzia de versões que depois vou ter que apagar…

Claro que é possível editar o título manualmente clicando no mesmo e a partir daí o Docs já não utiliza a primeira linha do texto… mas mesmo assim, será que não seria possível evitar a proliferação de sucedâneos?

Artigos Relacionados:

MP3: Procurar música no Google