Hi Tony, A few inline responses.
On Thu, Feb 16, 2017 at 11:22 AM, Tony Hirst <[email protected]> wrote: > Looking at the notes - We encourage users to start trying JupyterLab in > preparation for a future transition - I have a question re: the roadmap: > - will Jupyter notebooks continue to be available as such once Jupyterlab is > available? Yes. At some point it will become an optional component so you will need to enable it (and potentially disable lab if you don't want it). Both should coexist for some time. >(could a jupyterlab instance be configured to just mimic a simple > notebook UI, for example) Not yet. But that something I'd like to have as well. It's not a priority though. > - will Jupyterhub continue to supplort multiuser deployment of Jupyter > notebooks? Yes. JupyterHub does not really care of what is behind it. It already works with Lab. Ian is working on adding realtime multiuser collaboration, but that will be to Lab only. > 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. Lab is plugin based. You will need a non-default Lab. and activate only what you want. for your students. > 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. That's tough. Lab will probably not be completely ready this year (maybe ?) but we'll slow down on developing the classic notebook. Depending on your exact timescale and needs, I can see both being a good answer. > (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).) Kyle might be better person to answer for these timescale. > 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. Thanks for point of view and expressing your concern. We hope that the plugin-base approach can allow a (for example) jupyterlab-minimal to be available, which is sufficiently user-friendly until user are exprienced enough to move to "full". > > 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? When/if you try Lab, we'll greatly appreciate all your feedback on what seem unnatural. It's indeed hard to keep a newcommer eyes. Even best, if it's the first time you use it, if you can record your screen, and talk, then share the video (privately) with us, we can study it and look at what are the confusing, or non discoverable parts. Thanks, -- Matthias -- 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/CANJQusVz3FLEGmrS2USAak85QfPepy9pynSj2nZ9%3Dze1DnyyBw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
