Tony, Great questions and feedback! Inline thoughts below...
> - will Jupyter notebooks continue to be available as such once Jupyterlab is > available? (could a jupyterlab instance be configured to just mimic a simple > notebook UI, for example) Yes, the core JS component in JupyterLab are very well decoupled and designed to be used and reused in different ways. The JupyterLab team is very aware of the need to provide a UI that remains as simple as possible. Allowing individual notebooks to be edited in their own browser tab is *one* way of providing that. We have other ideas as well and will continue to explore these things for the 1.0 release and beyond. I spend much of my time teaching undergrads with the notebook and I know first hand how important it is to have something simple. > - will Jupyterhub continue to supplort multiuser deployment of Jupyter > notebooks? Yep, already works fine with JupyterHub. I have been using JupyterLab+Hub for the past 2 months in my data science course. Simply pip installing jupyterlab (and enabling its serverextension) was all that was needed. > > One of the attractions of Jupyter notebooks in education and for supporting > use of code outside computing discipline is that the notebook interface is > relatively simple and friendly without all the sidebar chrome and menus and > features and tools and stuff that make IDEs a terrifying experience for most > people. I'm keen to be able to keep using a simple clean interface from the > off with students and nontechies. Yes absolutely. Keeping JupyterLab simple while still providing the extra power has been one of my main design priorities. We are *not* there yet, but this is super important. > > I'm lobbying my institution to make notebooks available locally, a process > that will take 3-6 months to get deployed and then be expected to not change > much for a chunk of time. What should I be lobbying for?! I'm pitching for > novices to be able to access simple notebook UIs without any need for too > many features in the first instance. It depends on when you are doing this. If it was today, I would just stick with the classic jupyter notebook + jupyterhub. When JupyterLab comes out *midyear* (I don't know where Matthias got the idea it might be delayed until 2018 - that isn't the case), it should be easy to optionally add JupyterLab (literally just an extra pip install), but to keep classic notebook as well. Both run fine side by side in the same JupyterHub deployment and a user can pick which to use if both are installed. > > (eg if/when nteract ships with a bundled kernel, I can see it being great > for use with this user community (even more so if the ability to launch > temporary or multiuser nteract instances from a remote instituional server > accessed via a browser).) Yeah the most difficult thing to install is not the UI - but the kernels. > > By way of trying to express my general concerns, as opposed to just being > critical of the new... Looking at things like RStudio, it used to be > relatively simple... but as it gets richer features and more powerful tools, > and experts who've grown with it just have to keep up with it, and maybe > also demand more of it as they get more expert/professional, it just gets > more complicated and scary for novices coming to it for the first time. > Sometimes less is more. The on-ramp needs to be kept simple. (Or at least, > it helps if there is a simple on-ramp somewhere...). There are risks to > always developing more and moving away from the simple offering that > appealed to folk in the first place... Which isn't to say I don't like the > new features that appear with each new release of eg Jupyter notebooks and > isn't to say that Jupyter project shouldn't become an ever more powerful > tool for expert and power scientific computing users. +100. > > But it's easy to forget that the experience of welcoming new features as you > perceive they're missing, because you're growing in expertise as the tool > acquires more powerful features, is different to someone coming to the > environment for the first time - as a simple notebook that did what it did 3 > years ago, to the more complex notebook it is now, to the yet more complex > Jupyterlab view? Can you be more specific about the "complexity" here. I am not denying the notebook has become more complex or that JupyterLab is more complex than the notebook. But there are many types of complexities and I am interested about which you are thinking about here. Some that I can think of that could be an issue (in any software): * Multiple "acitvities" on a single page * Complexity of the code base * Visual complexity * Feature complexity (too many visual elements, too many borders, regions, colors, etc.) * Bad UI/UX design (distracting, overwhelming, etc.) Would love any specific concrete feedback you have on these things to help us refine JupyterLab. Cheers, Brian > > --tony > > On Wednesday, 15 February 2017 15:11:30 UTC, takowl wrote: >> >> Hi all, >> >> I've just released the first beta for Jupyter Notebook 5.0. Please try it >> out and let us know about any bugs. You can install it using: >> >> pip install --upgrade --pre notebook >> >> There isn't a headline big new feature in 5.0, but rather a range of new >> features and improvements. You can read about some of them here: >> http://jupyter-notebook.readthedocs.io/en/latest/changelog.html >> >> Thanks, >> Thomas > > -- > You received this message because you are subscribed to the Google Groups > "Project Jupyter" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jupyter/3d9410e4-096f-42a8-b5a7-43a88b5635d6%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub [email protected] and [email protected] -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAH4pYpTqvuP9VjrphGXdFmAGB%3DK%3DujtDbc-DWKoNyRc%3D8RwShA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
