News for hackers. Stuff that matters.
Re:First impressions of the IPython Notebook by jchendy on Friday September 06, 2013 @09:34AM (#6340317)
Does anybody have a similar data analysis workflow for languages other than Python?
Re:First impressions of the IPython Notebook by zokier on Friday September 06, 2013 @10:49AM (#6340709)
Julia is working on integrating to the IPython framework, see ijulia:

http://nbviewer.ipython.org/url/jdj.mit.edu/~stevenj/IJulia%...

Re:First impressions of the IPython Notebook by mistercow on Friday September 06, 2013 @12:00PM (#6341073)
Morespecifically, does anybody know of an attempt to do something similar in JavaScript (and ideally, languages that compile to it)? Having a notebook that could be entirely handled client side in a browser would be incredible.
Re:First impressions of the IPython Notebook by adw on Friday September 06, 2013 @02:02PM (#6341732)
TiddlyWiki is pretty near: http://tiddlywiki.com.

(the IPython Notebook is utterly, utterly wonderful. It's the first digital lab notebook worth a damn for data scientists.)

Re:First impressions of the IPython Notebook by jchendy on Friday September 06, 2013 @12:05PM (#6341102)
What type of work would you do with that? Are there any libraries available for real data analysis with JavaScript?
Re:First impressions of the IPython Notebook by mistercow on Tuesday September 10, 2013 @11:53AM (#6360778)
There are a few rather immature ones, but you can do a lot more with a notebook than just data analysis.

I often need to do calculations involving many parameters, and there are three important considerations I usually have to deal with:

1. I'm probably going to want to tweak the parameters.

2. The calculation is going to be difficult to express as a succinct equation.

3. I may want to look back over the result later.

Using an ordinary calculator is cumbersome because of 1 and 2, and doesn't satisfy 3. AN alternative is to use an ordinary interactive shell to put everything together, which helps with 2, but still makes for a lot of work on 1 and doesn't fix 3.

Writing a whole program to do the calculation is an improvement because it fixes 1 and 2, and it helps with 3 because I can leave myself lots of comments. I've found literate CoffeeScript to be very effective here (you can even turn it into a nice webpage to share your math with others), but there are still some drawbacks. The results are not interleaved with the code, so when I look back over it, it's not easy to check my work and debug. The workflow also leaves a bit to be desired. You can't, for example, quickly play with a small snippet as you're working through your thoughts.

A notebook, on the other hand, elegantly handles all of these considerations. I can use markdown to create a nice article for my future self explaining all of my calculations, have comments, code, and results all next to each other, and tweak parameters on the fly.

Yet I still find myself using literate CoffeeScript instead. And the main reason for that is that whenever I use Python, I constantly wish that I was using CoffeeScript instead.

Re:First impressions of the IPython Notebook by plessthanpt05 on Friday September 06, 2013 @10:37AM (#6340639)
the R community has recently & rapidly been building a notebook environment similar to that of the iPython notebook.
Re:First impressions of the IPython Notebook by carljv on Friday September 06, 2013 @12:19PM (#6341189)
Do they really need to develop a new environment? The IPython notebook environment can be adapted to different underlying language kernels--I think they've gotten the notebook at least partially working for Ruby and Julia. Why develop a whole new front-end just for R, instead of working with what's already an effective and tested environment?

I've had several conversations with R folks who insist that RStudio + Knitr does everything the IPython notebook does, and I feel like I've had a hard time conveying why I like the notebook for data exploration, prototyping, and demoing.

E.g., the R notebook linked to below looks neat, but it's still just markdown compiled to a static document. That's a different workflow--not a better or worse one; but certainly different.

Re:First impressions of the IPython Notebook by takluyver on Friday September 06, 2013 @12:29PM (#6341249)
People are certainly welcome to build an R kernel for the notebook. It could either be written in R, or you could write it in Python, subclassing the existing machinery to evaluate code with R using a library like rpy2.

Personally, I find it more interesting to mix languages in a single notebook - we have a %%R cell magic which allows you to have R cells in amongst your Python code, passing data between the two. An R kernel would only run R code.

Re:First impressions of the IPython Notebook by jchendy on Friday September 06, 2013 @10:57AM (#6340750)
Is this what you mean? Looks pretty cool. http://ramnathv.github.io/rNotebook/#