Live data from Hacker News

Estimating Number of Jupyter Notebooks on Github

kyso.io

51–60 of 135 posts

Re: Estimating Number of Jupyter Notebooks on Github

#51
We're seeing an explosion of Jupyter use as well on GitLab. GitLab already makes Jupyter easier to install on a Kubernetes cluster https://docs.gitlab.com/ee/user/project/clusters/#installing... In response to the growing demand we're doing two things:

1. Adding better Jupyter support to GitLab 12.0 https://gitlab.com/gitlab-org/gitlab-ce/issues/47138 as suggested by my co-founder.

2. Making it easier to do the entire data lifecycle with Meltano https://meltano.com/ which plans to include JupyterHub

Re: Estimating Number of Jupyter Notebooks on Github

#52

My two cents: We've been recently working in a FREE hosted version of Jupyter Lab mainly intended for education. Feel free to check it out. https://notebooks.ai/ Would love to hear some feedback.

> We've been recently working in a FREE hosted version [...]

Oh no, you make it sound like this is a good thing. It only means I can't take you serious.

Don't make it free. That is not a feature for a computation environment, it will only cause headaches on your side and people get wrong (bad) impression about the performance (assuming free accounts get some limited shared instances).

I rather pay a monthly fee for a good application, than a pseudo free instance, where you get limited resources. Do you have your credits forever?

Re: Estimating Number of Jupyter Notebooks on Github

#55

Earlier quoted context omitted.

Thats true if you sharing with someone who also understands the code - we think that the feature allows you to share the notebooks with a completely non-technical audience. Image you had a notebook to analyse sales data and you needed to present the results to your CEO (who perhaps cannot code) - this feature lets you present the notebook as is, without needing to prepare a report in some other format

Why would you share a notebook with somebody who doesn't understand the code?? What are they supposed to do with them anyways? Reading? Isn't that what PDF is for? Just give them PDFs, C*O people have got piles of other things to worry about besides shared notebooks.

Mostly so you don't need to convert to PDF and so that you can host the reports in a central place where everyone can read them technical or not.

Like an internal wiki for a companies data-science where the technical people can communicate their work to the non-technical people with a pretty seamless experience

Re: Estimating Number of Jupyter Notebooks on Github

#56

Earlier quoted context omitted.

The R community has built an incredible competing tool in RStudio and RMarkdown. You could argue that the progress of Jupyter is being held back by its ties to JSON as the serialization format for notebooks (which enables, among other things, the ability to serialize notebook execution output into the .ipynb vs. RMarkdown which does not). So the fairer comparison would be to compare .rmd vs. .ipynb instead of looking…

Can you imagine how much headache would have been saved if Jupyter was basically Rmarkdown with a less R-specific extension and a more general backend? After years with R I've been doing a lot of python work lately and UGH it feel like JupyterLab is a decade behind Rmarkdown. We wouldn't need special viewers in our source control frontend, or git hooks + tools like jupytext, or in-between editor plugins (VSCode)! By…

I totally agree with your sentiment. However, I also think that the popularity of Jupyter is largely due to the fact that it does appeal to a certain type of user.

I do believe that we have room for more than one option. The work that we've done in interactive programming in the Python VS Code extension is one possible approach that folks have seemed to like, and that aligns with what you're saying.

We're going to continue to explore that direction in addition to the Jupyter work that we're doing. Stay tuned!

Re: Estimating Number of Jupyter Notebooks on Github

#57
post #30

If you ever put notebooks in source control, you owe it to yourself to try the text-based notebooks supported in Visual Studio Code[1]. They're round-trippable with real (i.e. browser-based) notebooks, yet are much better for collaboration, diffing, and editing. [1] https://code.visualstudio.com/docs/python/jupyter-support

How does this compare to Jupytext? I prefer pipenv to Conda, and I don't like having Jupyter(Lab) installed in each venv separately, so instead I only add `Ipykernel` to each venv and then use my system-level JupyterLab to access per-project kernels; seems like that wouldn't work here?

Thanks for mentioning that project. I'm wasn't familiar with it, but the difference seems to be that Jupytext is a tool to convert notebooks between ipynb and text formats, while VSCode supports the same format (#%% cell delimiters) but enables you to edit text-based notebooks similar to how you would in the browser, including keyboard shortcuts to execute individual cells, it'll render the markdown, and so on.

I'm not sure if I understand your kernel question, but VSCode's Python extension has everything built-in. As soon as you add a #%% comment it considers what follows to be a notebook cell and automatically gives you a "run cell" button that uses your chosen Python interpreter.

Re: Estimating Number of Jupyter Notebooks on Github

#58

Earlier quoted context omitted.

The OP post is a Jupyter notebook itself and if you sign up to Kyso you can actually Jupyterlab on our cloud and the post the notebooks to the web, or make them private on the paid plan - is that what your looking for?

Yeah but unfortunately there is no GPU support. I wish there was!

Ah yeah ok - we are not planning GPU support soon - what if we created one of those one-click deploy a VM to aws/digital-ocean buttons and from there if you wanted to post to Kyso you could do it with git or our jupyter lab plugin.

You get most of the same experience and you can even customise various of the steps?

Re: Estimating Number of Jupyter Notebooks on Github

#59
post #30

If you ever put notebooks in source control, you owe it to yourself to try the text-based notebooks supported in Visual Studio Code[1]. They're round-trippable with real (i.e. browser-based) notebooks, yet are much better for collaboration, diffing, and editing. [1] https://code.visualstudio.com/docs/python/jupyter-support

Oh man, that's basically org-babel [0] but with working jupyter server support!

0: https://orgmode.org/manual/Working-with-Source-Code.html#Wor...

Post reply on HN