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

Show HN: A modern Jupyter client for macOS

satyrn.app

Post reply on HN
Print view View original

171–180 of 192 posts

Re: Show HN: A modern Jupyter client for macOS

#171

Post by crazygringo »

tomwphillips wrote: post #139
crazygringo wrote: post #101

Earlier quoted context omitted.

Yup, that's what "modern" means to me in this context. Thought it was totally clear. It looks like and acts like it was built for Sonoma, not for Sierra.

That didn’t occur to me. As an IPython/Jupyter user for over a decade and Mac user for two decades, it’s not something I personally care about or an issue I’ve felt.

Well sure, plenty of users don't care about aesthetics.

And the Jupyter notebook interface certainly isn't aesthetically pleasing. Colab is not as bad, but it's still not nice.

But some people do care about aesthetics, and this interface is actually aesthetically pleasing.

Re: Show HN: A modern Jupyter client for macOS

#172

Post by xaellison »

AnonC wrote: post #166

I do not see a privacy policy nor anything about telemetry, analytics or other data collection by the app. It would be good to clearly state what you’re collecting or not collecting. Without this, running such an app on a desktop OS seems a bit scary. I also hope you’re able to add something about the business model soon.

yeah this is an immediate show-stopper for me, at least for professional usage

Re: Show HN: A modern Jupyter client for macOS

#174

Post by PheonixPharts »

JBGruber wrote: post #165

A bit off topic, sorry, but: Jupyter is bad for research. The ability to run code out of order, but then save the output, is confusing for the one doing the research and everybody who wants to reproduce it. I don't understand why the decision was made for Jupyter to combine the source code of a notebook and the output. Things like Quarto keep both separate, as essentially all programming languages inteded, while prov…

This can be solved by just running "restart and re-run all" as a matter of habit whenever you feel like you are in a good state. If you're looking at someone else's notebook, this should also be your first step.

If you're using Python, Jupyter still offers a major advantage for sharing prototyping/research work in that it it is the only real way to provide literate programming. There are cases where code inside of a notebook should be pulled into a library, but pure code will always be inferior when most of your work is expository and exploratory.

Literate Haskell, and R Markdown are superior forms of literate programming, but Jupyter is not terrible if you just take some basic precautions before sharing.

Notebooks work great as... notebooks. Which is primarily how they're used in my experience. When the bulk of your work is prototyping and and exploring an idea, they're still an excellent choice.

Re: Show HN: A modern Jupyter client for macOS

#176

Post by nichochar »

madjam002 wrote: post #77

Is there something like Jupyter for Javascript/Typescript, ideally self hosted? At the moment I just do data science using one off scripts in NodeJS but seeing these notebook style formats recently where different chunks of code appear to be snapshotted and then visualisations can be easily integrated looks quite nice.

We are building one right now. It's very early and we have only "soft launched", but you can check it out here.

https://github.com/srcbookdev/srcbook

Re: Show HN: A modern Jupyter client for macOS

#177

Post by abdullahkhalids »

indrex wrote: post #175

When I first started coding, I wished there was an “app” for it where I just start writing code. Now there is.

I was taught coding on Matlab. It had everything built in, and no package management to worry about. As green freshmen, we were making games in week 2 of the course, and running science simulations soon after.

Re: Show HN: A modern Jupyter client for macOS

#178

Post by jackhodkinson »

mritchie712 wrote: post #164

This is great. I've wanted to build something similar many times, but like you've mentioned, it's tricky to monetize. Feature request: If I drag a tabular file (e.g. CSV, parquet, etc.) into the UI, do something like: temp1 = pd.read_csv('path_to_file') temp1.head() Good luck with it!

Thanks! That's a great idea. I have been thinking of doing something like this.

Re: Show HN: A modern Jupyter client for macOS

#180

Post by nerdponx »

randomlurking wrote: post #141
nerdponx wrote: post #126

Earlier quoted context omitted.

Do you have an existing workflow for that? I tried to set up some thing like that a couple years ago and couldn't figure out how to do it without copy-pasting the connection info JSON, which was not a comfortable workflow.

Im working exclusively with a remote connection (although inside the company network, so some security concerns don’t apply). I have Jupyter running as a service on Linux and am using a password instead of the generated token. So the URL stays the same and I don’t have to worry about anything much. The setup is working good for me - there are a couple of nuisances but they’re all related to the rest of my circumstanc…

Ah, so you have Jupyter itself running remotely? I was hoping you had a good workflow for starting or connecting to remote kernels using a local Jupyter frontend. This seems like such an obvious use case, but the ecosystem support for it is surprisingly poor. I've tried and failed several times over the years to figure out a workflow that a regular scientist or industry data analysit could follow.
Post reply on HN