I tried Jupyter Lab two weeks ago and found it to run unbearably slow. I'll try it again eventually I suppose, very well could have been a local issue
JupyterLab is ready for users
91–100 of 250 posts
Re: JupyterLab is ready for users
#92At the same time, the community has faced challenges in using various software workflows with the notebook alone, such as running code from text files interactively. The classic Jupyter Notebook, built on web technologies from 2011, is also difficult to customize and extend.
Do I read this correctly as hinting that Jupyter Notebook is being replaced by an IDE?
Re: JupyterLab is ready for users
#93Mathematica is wonderful in terms of sheer computational power, but the notebook interface it presents is hopelessly outclassed nowadays by initiatives such as these. I keep hoping Wolfram will spring some impressive new interface on us that will enhance usability for power users (rather than their weird attempts at bringing ‘computation’ to random casual users), but... I'm giving up hope. This looks very impressive.
Last time I've tried Jupyter, about a year or two ago, the user experience wasn't even close to that of Mathematica. I guess I'll give it another chance, but can you tell me in what way Mathematicas notebook interface is outclassed, in your opinion? The only major beef I have with Mathematica are its default stylesheets. They suck, every single one of them. There is no good distinction between input and output fields…
I agree here. Being able to write code in the mathematical rendering is such a beautiful feature of Mathematica that Jupyter is missing. I am not sure how it's outclassed as a notebook because of this. As an IDE? Sure, Mathematica's notebook isn't a good IDE at all. But as a notebook for writing mathematical statements, it's fantastic. It's the one thing I need in order to go to an only Julia workflow.
Re: JupyterLab is ready for users
#94Been trying to use JupyterLab over the weekend and had some issues with it. The idea is great though. I also look forward for the extensions. Data pipelines and dashboards can be built in visual applications much more quickly than with coding, so maybe we can now program extensions for that? Also, with vegalite and flask you can build dashboards from scratch and jupyterlab is great there (as you can mix code and notebooks). I think jupyterlab is very well positioned for being a complete end to end analytics tool from raw data to dashboards and visuals. If the extensions are powerful enough on the UI side, who knows? Maybe even business users could use jupyterlab.
Re: JupyterLab is ready for users
#95Earlier quoted context omitted.
I haven't used it much, but I believe you can do this by using (or more likely slightly extending) the init_cell nbextension. https://jupyter-contrib-nbextensions.readthedocs.io/en/lates...
Oh, that's cool - it's just some javascript that's essentially clicking execute on the selected cells. That makes sense, and hacked up version of this could work fine! Thanks!
If you get this working my cousin teaches elementary school and I'd love to show it to her! Please upload it if you're feeling generous :)
Re: JupyterLab is ready for users
#96At the same time, the community has faced challenges in using various software workflows with the notebook alone, such as running code from text files interactively. The classic Jupyter Notebook, built on web technologies from 2011, is also difficult to customize and extend. Do I read this correctly as hinting that Jupyter Notebook is being replaced by an IDE?
> JupyterLab 1.0 will eventually replace the classic Jupyter Notebook. Throughout this transition, the same notebook document format will be supported by both the classic Notebook and JupyterLab.
Guess so :-)
Re: JupyterLab is ready for users
#97Earlier quoted context omitted.
No, R and Python are fundamentally different. I do believe we will see a shift in what they are used for though. Python more for the "deep learning" stuff, and R for more statistical, non-deep-learning work.
Jupyter supports lots of languages (including R). RStudio is probably still nicer for working R, but I haven't done any serious analysis in R for a while now.
R Studio also support Python and a bunch of other languages as well. It'll be interesting to see how this all shakes out.
Re: JupyterLab is ready for users
#98I really hope they will add a panel to inspect current defined variables, like in Matlab, that would be so useful!
Re: JupyterLab is ready for users
#99This is the closest I've seen anyone actually deliver upon the promise of OpenDoc [1] and similar tech like KParts, but in a more user-accessible packaging. I'll be interested to find out its scalability and performance. If it renders only the part of a notebook that is visible, while continuing to run threaded computations of hidden components, then that might help some of the performance limitations I'm seeing people write about. That might be important to scale up collaboration as well in the future.
Re: JupyterLab is ready for users
#100I used the beta of Juypterlab and I was really impressed. Congrats on the Juypter team for releasing this! I was at Juypter Day at 2016 and they were talking about the roadmap to this feature. Its really exciting for this to come out!