News for hackers. Stuff that matters.
Re:What’s wrong with computational notebooks? by BeetleB on Tuesday January 28, 2020 @12:52AM (#22166792)
> Co-author of the study here. Let me know if you have any questions or how you overcome some of the problems we identified!

It's not clear who the audience is. It sounds like most people who complain about them are software people and not researchers/scientists.

For someone like me, who once did computational research using MATLAB, and later analyzed data for my job, Jupyter is not worse, and is in most ways superior. Let's take your points one by one:

> Participants stated they often downloaded data outside of the notebook from various data sources since interfacing with them programmatically was too much hassle.

This was the norm with MATLAB, Excel and JMP as well, unless someone wrote code to autodownload (extremely rare - less than 1% of people did that). And if you are going to write code to get the data from somewhere, it's much nicer in Jupyter than in these other tools.

> Not only that, but notebooks often crash with large data sets (possibly due to the notebooks running in a web browser).

I honestly have not seen this, and the reason makes no sense. Your browser is not handling the data. The kernel is. I mean yes, if you try to load several GB of data in pandas, it's possible you will have problems if you run out of RAM, but this has nothing to do with notebooks.

> Once the data is loaded, it then has to be cleaned, which participants complained is a repetitive and time consuming task

This was as much a problem prior to notebooks as it is now. Notebooks did not make this any worse.

> Explore and analyze. Modeling and visualizing data are common tasks but can become frustrating. For example, we observed one participant tweak the parameters of a plot more than 20 times in less than 5 minutes.

It was even worse with MATLAB. Ditto for Excel. JMP is a bit nicer for visualization, though.

> Notebooks do not have all of the features of an IDE, like integrated documentation or sophisticated autocomplete, so participants often switch back and forth between an IDE (e.g., VS Code) and their notebook.

It may be better now, but this was a problem in MATLAB as well.

> While it is easy to share the notebook file, it is often not easy to share the data.

This is as true with MATLAB, JMP, etc. A lot of the complaints about it being hard to reuse notebooks is because notebooks at least attempt to be reproducible, and thus many more people attempt it. Prior to notebooks, I know almost no one who tried to share MATLAB analyses, because it was such a pain to do so.

> Notebooks as products. If a large data set is used, as one might expect in production, then the notebook will lose the interactivity while it is executing. Also, notebooks encourage "quick and dirty" code that may require rewriting before it is production quality.

I suppose some people are trying to make products out of notebooks, and this is where all the recent grief I see is coming from. I do not think it was the primary goal of notebooks, though. They were meant for data analyses and prototyping, not for production use.

Re:What’s wrong with computational notebooks? by dkersten on Tuesday January 28, 2020 @04:11AM (#22167729)
Much of your comment could be summarised as “it’s no worse than prior tools”. That doesn’t invalidate the authors points though: just because it’s better than previous tools, which have the same or worse problems, doesn’t mean notebooks don’t have problems that should perhaps be tackled or talked about. That it’s an improvement over what existed before doesn’t mean you can’t be critical about the flaws it still has and a study like this (looking at real people) and discussion like we’re having here is a necessary start to finding out how to improve on this.
Re:What’s wrong with computational notebooks? by scott_s on Tuesday January 28, 2020 @11:01AM (#22170555)
> It's not clear who the audience is.

People who design and implement features in notebooks. The conclusions in the blog post and research paper are clear that improving these identified problems could improve user experience.

Re:What’s wrong with computational notebooks? by paulgb on Tuesday January 28, 2020 @06:57AM (#22168549)
> I honestly have not seen this, and the reason makes no sense. Your browser is not handling the data. The kernel is. I mean yes, if you try to load several GB of data in pandas, it's possible you will have problems if you run out of RAM, but this has nothing to do with notebooks.

This is true nowadays with Jupyter, because it is smart about truncating output. But it used to be possible to OOM the browser by e.g. printing in an long-running loop or displaying too long of a list/table.

Re:What’s wrong with computational notebooks? by BeetleB on Tuesday January 28, 2020 @10:28AM (#22170233)
Mostly I used pandas Series/Dataframes, and they've always had built-in protection for not printing too much.

But I guess if you're manually printing in a for-loop, then I suppose you could make the browser crash - whereas tools like MATLAB wouldn't.

Re:What’s wrong with computational notebooks? by djrobstep on Tuesday January 28, 2020 @02:52AM (#22167300)
Why so defensive?
Re:What’s wrong with computational notebooks? by mirekrusin on Tuesday January 28, 2020 @03:46AM (#22167613)
Maybe because of the negative sentiment/bad taste statements like "What's wrong with..." leave. It could say "What can be improved with ... in 2020" instead. Probably not intention of the author but it comes as non-constructive crtiticism/"not recommended to use" a bit too much. Some observations seem to not be directly related to notebooks per se. Other feel like could be made as just entries in a FAQ/best practices section of documentation.

Kudos for looking at real people's work and surveying it.

I wonder how much workflow could be improved if researchers would be temporarily paired with developers - who are generally better at modularising and removing friction in their work.

Personally I believe that a bit of clean-code discipline and following known best practices could solve couple of those pain points.

It's also true some could be improved by rethinking how notebooks work; ie. being able to specify input/output of notebook so it can be used as a library; detaching runtime data from the code so it plays better with version control/publishing; maybe even more radical ideas like adding visual/flow view that helps with linking elements; adding built-in excel-like sheets that can be queried/manipulated could also be interesting; built-in, first class support for relational database (sqlite) could also be a big win.

There are many interesting developments happening in this space and there seem to be some unexplored ideas waiting to be tested out.

Re:What’s wrong with computational notebooks? by bipson on Tuesday January 28, 2020 @05:17AM (#22168015)
"What's wrong with ..." for me literally means "What should be done about ..." or "How to make ... better".

I found your defense, which basically just says "It wasn't better before - so, no critique allowed?", considerably less valuable than the article.

Re:What’s wrong with computational notebooks? by PeterisP on Tuesday January 28, 2020 @06:03AM (#22168240)
IMHO "What's wrong with ..." in colloquial use usually means "Here's a bunch of reasons why you shouldn't use ...".