What was the earliest of these tools? Mathcad? Mathematica? Maple?
Why Jupyter is data scientists’ computational notebook of choice
21–30 of 308 posts
Re: Why Jupyter is data scientists’ computational notebook of choice
#22Most editors can't open a terminal that you can use VIM keybindings on to search/navigate history and treate like any other buffer.
VSCode -> not currently possible because they wrote it in a restrictive way with Panel as a special case very different to code window Atom -> probably possible but I don't think terminal-plus is quite it. Any IDE I've tried -> not possible. Emacs -> possible.
Not that this is the be all end all feature but it is useful as hell and kind of a litmus test for whether you can program your environment.
edit: LightTable seemed kind of cool but became abandonware like the author's other projects
Re: Why Jupyter is data scientists’ computational notebook of choice
#23I like R for many things, but Python just keeps getting more compelling, particularly given the excellent machine learning packages. As these sorts of toolchain elements get better and better, and as more people realize that there's a benefit to simultaneously training researchers to run code as well as stats, I suspect we'll start to see an exodus from pure R solutions. The real question is when (and whether) new so…
Re: Why Jupyter is data scientists’ computational notebook of choice
#24How do people cope with this? Do you supplement it with other tools? I spend a lot of my time in an IDE and then just paste some of the code in to cells. That seems easier.
Re: Why Jupyter is data scientists’ computational notebook of choice
#25The only thing that stops me from being able to use notebooks full time is their intellisense compared to IDEs is horrible. I like being able to use them for demos/presentations, but I can't imagine trying to code within one primarily. Especially when it comes to tracking results. How do people cope with this? Do you supplement it with other tools? I spend a lot of my time in an IDE and then just paste some of the co…
Re: Why Jupyter is data scientists’ computational notebook of choice
#26The only thing that stops me from being able to use notebooks full time is their intellisense compared to IDEs is horrible. I like being able to use them for demos/presentations, but I can't imagine trying to code within one primarily. Especially when it comes to tracking results. How do people cope with this? Do you supplement it with other tools? I spend a lot of my time in an IDE and then just paste some of the co…
If you're writing a lot of code in them, it's probably better to put that code into libraries that get imported and reused.
And I do agree that default code environment is unbearable. Particularly the auto insertion of completing quotation marks, which has me continually fighting with the editor to get correct code into a tiny web text box.
Re: Why Jupyter is data scientists’ computational notebook of choice
#27The only thing that stops me from being able to use notebooks full time is their intellisense compared to IDEs is horrible. I like being able to use them for demos/presentations, but I can't imagine trying to code within one primarily. Especially when it comes to tracking results. How do people cope with this? Do you supplement it with other tools? I spend a lot of my time in an IDE and then just paste some of the co…
Re: Why Jupyter is data scientists’ computational notebook of choice
#28I've switched largely to Jupyter / Python for computational linguistics / psycholinguistics because of the pandas / numpy /numba stack, decent off-the-shelf NLP (spacy and gensim), and the ease of moving data into an R kernel for specific analyses and plots. Also nice that any reasonably sized notebook will render on GitHub (and access can be controlled through the accounts system, until something is ready to be publ…
Yes! Juypter notebook has an export to .tex file in its export menu. If you install the right stuff you can render the output on the server. However, the output of this isn’t nearly as well formed as a hand written latex document is.
Re: Why Jupyter is data scientists’ computational notebook of choice
#29The only thing that stops me from being able to use notebooks full time is their intellisense compared to IDEs is horrible. I like being able to use them for demos/presentations, but I can't imagine trying to code within one primarily. Especially when it comes to tracking results. How do people cope with this? Do you supplement it with other tools? I spend a lot of my time in an IDE and then just paste some of the co…
Work (and often debug) in jupyter -> open the notebook from pycharm when it's got some completed thoughts and write into a python module + test module, tidying up and adding type annotations.
Sometimes doing that multiple times so that the notebook is importing from modules which were originally pulled out of the notebook.
It sucks having to use two tools but I don't think there's any one tool that can do both as well as pycharm/jupyter, short of me getting a lot better at emacs or writing a lot of custom Atom extensions (I think).
Re: Why Jupyter is data scientists’ computational notebook of choice
#30The only thing that stops me from being able to use notebooks full time is their intellisense compared to IDEs is horrible. I like being able to use them for demos/presentations, but I can't imagine trying to code within one primarily. Especially when it comes to tracking results. How do people cope with this? Do you supplement it with other tools? I spend a lot of my time in an IDE and then just paste some of the co…
P.S. Disclaimer: I lead this project at JetBrains, Inc.