Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JupyterLite – WASM-powered Jupyter running in the browser

github.com

Post reply on HN
Print view View original

21–30 of 68 posts

Re: JupyterLite – WASM-powered Jupyter running in the browser

#21

Post by [deleted] »

throwaway894345 wrote: post #12
ktpsns wrote: post #2

Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.

> I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices. If you’re working with data of any significant size at all it then it doesn’t matter how fast your user device is—it’s so much cheaper (time and network egress costs) to send the computations from a user device to the cloud t…

[deleted]

Re: JupyterLite – WASM-powered Jupyter running in the browser

#22

Post by otabdeveloper4 »

throwaway894345 wrote: post #12
ktpsns wrote: post #2

Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.

> I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices. If you’re working with data of any significant size at all it then it doesn’t matter how fast your user device is—it’s so much cheaper (time and network egress costs) to send the computations from a user device to the cloud t…

You definitely shouldn't be running this stuff from a Jupyter notebook.

Re: JupyterLite – WASM-powered Jupyter running in the browser

#23

Post by fmajid »

youngtaff wrote: post #8
fmajid wrote: post #7

Earlier quoted context omitted.

No, WASM gets compiled to native code

Java bytecode got translated to native too Think we've just got better at runtimes over time (JIT, intermediate formats etc.) and WASM was designed to be good for this rather than needed to work with an already exising bytecode

Reflection and other language features preclude direct translation of Java bytecode to machine code, whereas WASM is designed to be a portable assembly language, closer to the IL of GCC or LLVM.

Re: JupyterLite – WASM-powered Jupyter running in the browser

#24

Post by throwaway894345 »

mrtesthah wrote: post #19
throwaway894345 wrote: post #17

Earlier quoted context omitted.

I don’t believe that the majority of Jupyterhub users are “consumers” rather than professionals, but more importantly, that doesn’t change the fact that the professional use case exist and isn’t amenable to the fat client approach. As an anecdote, I work on a Jupyterhub managed service offering with customers in both the private and public sectors and our data sizes are pretty much all in this range.

> I work on a Jupyterhub managed service offering ... That sounds like selection bias.

It might be. Like I said: anecdote.

Re: JupyterLite – WASM-powered Jupyter running in the browser

#25

Post by throwaway894345 »

otabdeveloper4 wrote: post #22
throwaway894345 wrote: post #12

Earlier quoted context omitted.

> I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices. If you’re working with data of any significant size at all it then it doesn’t matter how fast your user device is—it’s so much cheaper (time and network egress costs) to send the computations from a user device to the cloud t…

You definitely shouldn't be running this stuff from a Jupyter notebook.

Why not? We make a lot of money offering it to people.

Re: JupyterLite – WASM-powered Jupyter running in the browser

#26

Post by otabdeveloper4 »

throwaway894345 wrote: post #25
otabdeveloper4 wrote: post #22

Earlier quoted context omitted.

You definitely shouldn't be running this stuff from a Jupyter notebook.

Why not? We make a lot of money offering it to people.

Yes, the market in enabling people to do the "you shouldn't be doing this" stupid things is huge.

Re: JupyterLite – WASM-powered Jupyter running in the browser

#27

Post by jcims »

ktpsns wrote: post #2

Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.

Unfortunately we will need more cloud computing. If you're watching what's going on in the ransomware and cyber insurance space, small and many medium-sized companies that require E&O coverage for their contracts are not going to be able to afford to run on their own equipment.

Re: JupyterLite – WASM-powered Jupyter running in the browser

#28

Post by throwaway894345 »

otabdeveloper4 wrote: post #26
throwaway894345 wrote: post #25

Earlier quoted context omitted.

Why not? We make a lot of money offering it to people.

Yes, the market in enabling people to do the "you shouldn't be doing this" stupid things is huge.

Any substance on why we shouldn’t be doing it or why it’s stupid? What’s the alternative? Should researchers all learn Kubernetes and AWS and deploy their own environments?

Re: JupyterLite – WASM-powered Jupyter running in the browser

#29

Post by codefreakxff »

rerx wrote: post #9
ipsum2 wrote: post #6

Earlier quoted context omitted.

What do you like about nteract over Jupyter's frontend? The website is devoid of details.

It's convenient to directly open a notebook from a browser download or a slack message without having to fire up jupyter in a terminal and navigate it to that temp file.

I use vscode to open and run notebooks using the jupyter plugin. Works great. Don’t need to fire up the browser

Re: JupyterLite – WASM-powered Jupyter running in the browser

#30

Post by otabdeveloper4 »

throwaway894345 wrote: post #28
otabdeveloper4 wrote: post #26

Earlier quoted context omitted.

Yes, the market in enabling people to do the "you shouldn't be doing this" stupid things is huge.

Any substance on why we shouldn’t be doing it or why it’s stupid? What’s the alternative? Should researchers all learn Kubernetes and AWS and deploy their own environments?

The problem with Jupyter is that it impedes common-sense practices like version control, reproducibility, and automation.

If you're spending the time and effort to rent these big servers, why not spend the 5 percent of the effort and do it right?

Jupyter exists mostly because analytics/math guys are too lazy to spend a day learning software development practices. Must be some sort of us-vs-them point of misplaced pride.

Post reply on HN