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

Launch HN: Moonglow (YC S24) – Serverless Jupyter Notebooks

news.ycombinator.com

Post reply on HN
Print view View original

51–58 of 58 posts

Re: Launch HN: Moonglow (YC S24) – Serverless Jupyter Notebooks

#52

Post by fluxode »

Two questions:

1. How is this different from Syncthing and similar solutions? Syncthing is free, open-source, cloud agnostic and easy to use to accomplish what seems to be the same task as Moonglow. 2. What is serverless about this? It is not clear from the pitch above.

Re: Launch HN: Moonglow (YC S24) – Serverless Jupyter Notebooks

#54

Post by bblcla »

fluxode wrote: post #52

Two questions: 1. How is this different from Syncthing and similar solutions? Syncthing is free, open-source, cloud agnostic and easy to use to accomplish what seems to be the same task as Moonglow. 2. What is serverless about this? It is not clear from the pitch above.

1. It looks like Syncthing is an application that lets you sync files? Moonglow runs one layer below - we call cloud apis for you, to set up and connect you to a remote Jupyter kernel.

2. I think the serverless here is actually pretty literal - you don't have to think about or spin up a Jupyter server. We normally describe it as 'run local jupyter notebooks on your own cloud compute,' which I think might be a little more clear.

Re: Launch HN: Moonglow (YC S24) – Serverless Jupyter Notebooks

#55

Post by whinvik »

bblcla wrote: post #34
whinvik wrote: post #29

Feels a bit like what Databricks already does with Dbx etc.

I'm not super familiar with dbx (though its docs at https://docs.databricks.com/en/archive/dev-tools/dbx/dbx.htm... suggest it's deprecated). However, looking at its replacement here ( https://docs.databricks.com/en/dev-tools/bundles/index.html ) - I think we're trying to solve the same problems at different levels. My guess is Databricks is the right solution for big teams that need well-defined staging/prod/dev env…

Thanks. I did not know dbx was deprecated and replaced.

Wouldn't targeting smaller teams lead to a lot of pricing pressure? Or do you think there's enough volume to justify that?

Re: Launch HN: Moonglow (YC S24) – Serverless Jupyter Notebooks

#56

Post by geysersam »

OvbiousError wrote: post #37
dinobones wrote: post #27

Earlier quoted context omitted.

I too share the dream of transpiling everything/WebAssembly/everything can run everywhere, but we're pretty far. For a lot of ML/AI workloads and tasks, Python is just a binding for underlying C/C++. It's already a nightmare to try to reproduce any ML/AI paper, pip breaks 3 times, incompatible peer deps, some obscure library emits an obscure CLANG error that means I need to brew install some libwhatever, etc... I don…

The performance of browser wasm is also incomparable to the same code compiled into a native binary.

What kind of slowdown would you expect on equivalent hardware?

Re: Launch HN: Moonglow (YC S24) – Serverless Jupyter Notebooks

#57

Post by mistrial9 »

nickagliano wrote: post #51
mistrial9 wrote: post #21

"Don't fork the Notebook format" --Fernando

I saw this comment on the marimo post too. Is there a source of Fernando saying this?

there have been Jupyter team meetings at UC Berkeley since the times of ipython Notebook. Fernando Perez is the source of that quote.. ask someone on the core team ?
Post reply on HN