This is an ad.
Deepnote, a Jupyter alternative, is going open source
71–80 of 179 posts
Re: Deepnote, a Jupyter alternative, is going open source
#72Way to undermine an interesting product launch through poorly chosen language: > Let’s be frank the single‑player notebook has felt outdated for a while now. We’re open‑sourcing its successor. Jupyter belongs in the hall of great ideas — alongside “Hello, world.” and “View Source.” If you're trying to reach out to the Python community this is not the way to do it. Completely unnecessary hostile language there! Have s…
When we stand on the shoulders of giants, we don’t do so to dump on them.
Re: Deepnote, a Jupyter alternative, is going open source
#73I'm Jakub, CEO of Deepnote. Didn't expect to see this trending here! We worked hard to execute on our vision of a data notebook and I'm glad we finally got a chance to open source it. We stand on the shoulders of giants. AMA!
Which LLM was used to generate that post?
Re: Deepnote, a Jupyter alternative, is going open source
#74It's telling that Wolfram / Mathemetica doesn't even come up in a blog post like this, as the inventors of "the notebook". Jupyter took the concept to a whole new level, but the concept did originate in Mathematica 30 years ago!
Re: Deepnote, a Jupyter alternative, is going open source
#75The article reads as if generated by AI. Lol
Re: Deepnote, a Jupyter alternative, is going open source
#76> Teams need notebooks that are reactive, collaborative, and AI‑ready reactive: this matters, but all the alternatives have it collaborative: this matters very little in the Figma / Google Docs sense of collaborative in practice. It's very rare you want two people working on the same notebook at the same time. What you really want is git style version control. AI‑ready: you want something as close to plain python (wh…
This is the first time I'm hearing about marimo and i have to say their landing page is excellent! Immediately makes me want to try it
Re: Deepnote, a Jupyter alternative, is going open source
#77Are there any other people who hate notebooks? Give a plain old script anytime. Run and edit anywhere without extra packages or even a Web browser.
I do think notebooks are very flawed right now even if the concept is sound. Right now they are essentially an IDE without the ability to produce publishable output (you are literally expected to ship the project in the form the IDE works with) and they are not a very good IDE at that.
They need reliable dedicated published output fit for general public consumption. This means a static (no backend host required) sharable .html file where end users can view all the data and run the code samples that doesn't try to present as an IDE. I actually wrote https://rubberduckmaths.com/eulers_theorem in Jupyter but had to manually copy and paste to a new well formatted static html file and re-paste the code blocks into Pyodide enabled text areas within that html since the export functionality is a mess. The result of the manual work means i now have an easily sharable and easily hosted static html file with working Python code samples as it should be but... Why don't Notebooks have a published form like this already? It seems pretty obvious that Notebooks are your IDE, they shouldn't be the output you present. We're literally asking users today 'to view this notebook install Jupyter/Marimo/whatever and open from there' when the Notebook is designed to create the publication rather than a place to view it. In general the output i demonstrate above should be the minimum bar that Notebook 'export' features should hit. Export as a static .html file with working code. As someone who manually 'compiles' notebooks it's not hard to do yet Notebooks simply don't have an actual working html export right now (i know there's technically a 'html' export option in Jupyter but it will strip out your code and create a terribly poorly formatted document as output).
The IDE aspects themselves, at least for Jupyter (the one I've tried out the most), are a bit too simple too. Yes it's nice to have alternating 'text' blocks followed by 'code' blocks but that's really all they are right not. I want something more complex. I want the code blocks shown to actually be windows to a full python project. Users should be able to change the code shown and view the larger, well structured Python code. Right now it's text, followed by simple code. Not much more honestly. As it is right now i feel Notebooks only work for really simple projects.
If you have a complex Python project i agree the way to only share it is to share the Python project as is. Notebooks could be a wonderful explanatory wrapper to a larger project but right now they just aren't good at doing much more than the simple 'here's some data' followed by 'here's the code i used to process that data' and they don't even present that particularly well.
Re: Deepnote, a Jupyter alternative, is going open source
#78Earlier quoted context omitted.
I have no real qualms with the idea of a notebook, as long as it's not adding a lot of custom magic. I should be able to share what I'm working on, iterate in a notebook with someone, then extract it into a standalone program without much thought.
One issue is that very often the "magic" happens in imported modules, so you can't really see what is happening unless you drop down to a text editor anyway. Then there is the infamous issue of modules not automatically reloading even when rerunning the Notebook.
That in theory shouldn't be too bad. Though, there have been some things like %sql I remember using in one notebook, which was essentially a macro for making a datatable from a SQL expression, but it wasn't something you could just copy directly.
Re: Deepnote, a Jupyter alternative, is going open source
#79> Teams need notebooks that are reactive, collaborative, and AI‑ready reactive: this matters, but all the alternatives have it collaborative: this matters very little in the Figma / Google Docs sense of collaborative in practice. It's very rare you want two people working on the same notebook at the same time. What you really want is git style version control. AI‑ready: you want something as close to plain python (wh…
I'd argue the opposite.
There is plenty of AI extensions, but the experience matters. The depth of integration matters. When you execute queries against production warehouses and you make decisions based on the results of AI-generated code, accuracy matters. We had our first demo of an AI agent running in 2 days, it took us another 2 years to build the infrastructure to test it, monitor it, and integrate it into the existing data source.
You'd be surprised how many people collaborate together. Software engineering is solitary, collaboration happens in GitHub. But data analysis is collaborative. We frequently have 300+ people looking at the same notebook at the same time.
.py never worked for data exploration. You need to mix code, text, charts, interactive elements. And then you need to add metadata: comments, references to integrations, auth secrets. There are notebooks that are several pages long with 0 code. We are building a computational medium of the future and that goes beyond a plaintext file, no matter how much we love the simplicity of a plaintext file.
Re: Deepnote, a Jupyter alternative, is going open source
#80Way to undermine an interesting product launch through poorly chosen language: > Let’s be frank the single‑player notebook has felt outdated for a while now. We’re open‑sourcing its successor. Jupyter belongs in the hall of great ideas — alongside “Hello, world.” and “View Source.” If you're trying to reach out to the Python community this is not the way to do it. Completely unnecessary hostile language there! Have s…
>If you're trying to reach out to the Python community this is not the way to do it. Completely unnecessary hostile language there! Have some respect.
The note sounds as written by some manager/marketing guy that has 20 years to touch a line of code...
For sure it put my off even checking what their shit is (from initially interested upon seeing the HN post).