Those sliders look sweet :)
JupyterLab is ready for users
51–60 of 250 posts
Re: JupyterLab is ready for users
#52I'll be teaching a group of nine and ten years olds to code. I'm planning on using Jupyter. What I'd really like to do is make a multiplayer naval game, with each player controlling their ship from their own notebook. Players would start out by running commands like fire(range=400, bearing=120) right from a cell, but would later be able automate their ship - for example, pick the nearest enemy, get the range, and plu…
> multiplayer navel game
I don't think you mean this, though it could be intriguing just as well..
Re: JupyterLab is ready for users
#53I'm trying to get a JupyterHub or JupyterLab instance deployed at my university. JupyterHub has documentation on deployment, authentication (e.g,. LDAP, CAS), and so on. I'm guessing that JupyterLab will eventually get things like this. Does anyone know if there will be a migration path for JupyterHub to JupyterLab?
Re: JupyterLab is ready for users
#54I'll be teaching a group of nine and ten years olds to code. I'm planning on using Jupyter. What I'd really like to do is make a multiplayer naval game, with each player controlling their ship from their own notebook. Players would start out by running commands like fire(range=400, bearing=120) right from a cell, but would later be able automate their ship - for example, pick the nearest enemy, get the range, and plu…
> multiplayer navel game I don't think you mean this, though it could be intriguing just as well.. https://en.wikipedia.org/wiki/Omphaloskepsis
Nope! Thanks for the catch!
Re: JupyterLab is ready for users
#55I'll be teaching a group of nine and ten years olds to code. I'm planning on using Jupyter. What I'd really like to do is make a multiplayer naval game, with each player controlling their ship from their own notebook. Players would start out by running commands like fire(range=400, bearing=120) right from a cell, but would later be able automate their ship - for example, pick the nearest enemy, get the range, and plu…
The simplest (and still educational) way would be to have the stuff in the different cells as functions, and to collect all the functions that should be re-run in a single cell.
To do it more properly, however, you can have a post_save_hook for the whole notebook, which runs the code from whichever cells however often you want outside of the notebooks. Of course, this way you wont see the output in the notebook.
Re: JupyterLab is ready for users
#56I'm trying to get a JupyterHub or JupyterLab instance deployed at my university. JupyterHub has documentation on deployment, authentication (e.g,. LDAP, CAS), and so on. I'm guessing that JupyterLab will eventually get things like this. Does anyone know if there will be a migration path for JupyterHub to JupyterLab?
JupyterHub is the multi-user application which will proxy a single user application. Jupyter notebook is the default single user app, but it can be configured to use jupyterlab.
Re: JupyterLab is ready for users
#57Mathematica 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…
Yours is a good question, and I can't really provide a good answer. Firstly, I suppose I wish for something more akin to an IDE with a proper list of variables, functions, classes, & cetera; tabs; and as the screenshots of this JupyterLab beta release show, a capability for displaying different data types in different self-contained windows that are not in-lines to the notebook document.
I probably expressed myself very poorly.
Re: JupyterLab is ready for users
#58I'd really like 1 thing from those articles. I didn't knew what Jupyter was in first place.
So please dear authors when I click on your articles I'd like to have a single sentence somewhere on the landing zone where I can easily figure what we're talking about and not having to read entire paragraphs
Thanks,
Re: JupyterLab is ready for users
#59How does this affects the other environments? Will this be the demise of R Studio?
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.
Re: JupyterLab is ready for users
#60There is only one mention of Python in the entire post... there are 5 mention of JavaScript. Recently, I have been mulling over the GUI creation problems and packaging problems that still plague the Python ecosystem. That being just the start of it...
I guess my love affair with Python is souring a bit. Compared to JavaScript it seems like it has slowed to a crawl on the innovation front. That is, for anything NOT related to machine learning.
I use Jupyter notebooks with Python all the time and only recently started using them with Node.js it seems like JS is just killing it...