Can you have provide any examples of the scenario you described?
631 karma · joined April 7, 2023
prasoon [at] getlumen [dot] dev
Can you have provide any examples of the scenario you described?
Not sure what more we could have said to make it absolutely clear that Pretzel is a fork of Jupyter but here's the first line of our Show HN post today:
> We’ve forked Jupyter Lab
Here's the first line of our README
> Pretzel is a fork of Jupyter with the goal to improve Jupyter's capabilities
Here's the first line of our LICENCE file
> Pretzel is a fork of Project Jupyter, which is licensed under the terms of the Modified BSD License.
I'm happy to add this to more places if you think it would make it clearer for people.
If you wouldn't mind, can you please comment on this issue so we can ask a few follow-up questions to help in debugging this issue?
If you've used jupyter-ai, I'd really appreciate if you can try out Pretzel and tell us if you're missing anything. We definitely are behind on the number of integrations and as you say, jupyter-ai codebase is more mature but I really think we've a made a much more usable tool.
I'll also copy what I said in another comment: In short, for now, yes might have been able to implement this functionality as an extension (though there are several other changes that we've made to core Jupyter behavior as well). But our roadmap calls for much more sweeping changes to the code execution model itself and that simply cannot be an extension.
In short, for now, yes might have been able to implement this functionality as an extension (though there are several other changes that we've made to core Jupyter behavior as well). But our roadmap calls for much more sweeping changes to the code execution model itself and that simply cannot be an extension.
At the moment, the system prompt is hardcoded in code. I don't think it should bias analyses because our goal is usually returning code that does something specific (for eg "calculate normalized rates for column X grouped by column Y") as opposed to something generic ("why is our churn rate going up"). So, the idea would be that the operator is responsible for asking the right questions - the AI merely acts as a facilitator to generate and understand code.
Also tangentially, we do want to allow users some king of local prompt management and allow easy access, potentially via slash commands. In our testing so far, the existing prompt largely works (took us a fair bit of hit-and-trial to find something that mostly works for common data usecases) but we're hitting limitations of a fixed system prompt so these links will be useful.
By making a fork that can be installed in one line of code, we're hoping that we don't make Jupyter user's go through decision fatigue for yet another dev tool. Instead, the idea is to simply make their existing tool better.
Jupyter is a web application that lets a user execute python code in either a local or remote "kernel" - which is just a Python process with a communication layer.
You can then do literate programming (meaning run some code and immediately see results including plots and tables) within this web interface. Basically a much fancier REPL. The code can run either locally on your machine or remotely in the aforementioned python "kernel".
Here's a quick introduction to Notebooks that I found on YouTube: https://www.youtube.com/watch?v=jZ952vChhuI
As of now though - there are plenty of people who do use Jupyter and we hope Pretzel - as it stands today - can already be of help to them.
The AI mode/box with Cmd + K is for more complex prompts, multi-line code chunks and such. We've tried to make everything completely keyboard accessible btw, including the sidebar so that you never have to use the mouse :)
We haven't tried vs Sonnet 3.5 yet - my hunch is that on the speed/quality/cost space, Sonnet will end up doing better than Codestral for some folks.
Against general purpose local models (taking Llama-70B as a high-water mark), Codestral does better far better on code related tasks while being less than 1/3rd the size (22B!). That said, I'm definitely exited to try out DeepSeek Coder v2 - by all reports, it's amazing model for code completion and will likely also beat out Codestral.
I don't think we're planning to fine-tune Codestral though (or any model for that matter). The latest models keep on becoming faster, better and cheaper AND they already work quite well. My thinking at this time is that waiting it out and having a big AI lab make a more capable general model is a better strategy.
I'd be curious to hear a bit more about the kind of work you do that made you switch. Also if there's anything you miss in VSC/Cursor vs Jupyter. If you don't mind a small email exchange, let me know and I'll drop you a message :)
Also, as we build more features, we're definitely going in the direction of more analytics workloads (live collaboration, leaving comments, google-doc type versioning, fully AI driven analyses similar to OpenAI Interpreter mode etc) and with these features, I think there will be a clear divergence of feature-set in VSCode/PyCharm vs Pretzel.
If I may ask, are you more on the engineering side (MLE) or more on the data side (Data Analyst)? EDIT: Just saw your other comment!
Thanks for the kind words, we're exited to be building this :)
- https://noteable.io/ - as you say, it doesn't exist anymore
- https://deepnote.com - Deepnote is closed source sadly - you can't run it locally, you can't tweak it, you need to learn a new interface and switch to it
- https://github.com/jupyterlab/jupyter-ai - I actually mentioned this in the post but in my experience, the UX and features are far behind what we've built already. I'd love to hear from anyone who's tried jupyter-ai to give us a shot and let me know what we're missing! The plus side of jupyter-ai is of course that it supports way more models and the codebase is a lot more hackable than what we've built.
- https://colab.google/ - closed-source, similar challenges as with Deepnote. Another big challenge is that if you want to use Colab as a company, AFAICT, you need use their enterprise version (so that you can have native data collectors, support guarantees etc) and that only works with GCP so if you're an AWS shop, this might be a deal-breaker.
- https://cocalc.com - hadn't used it so far but congrats on a great project! Will check it out. Didn't look in detail but first impressions makes it look like a fairly different interface from Jupyter. One of our goals was to go to where the users already are - that meant Jupyter. So that's definitely a major difference.
- VSCode - as I've mentioned elsewhere, we're targeting a more of an analytics usecase with the features we're building. VSCode has AI features of course! But we'll look quite different once we build more items on the roadmap :)
Selecting the license for an open-source tool backed by a company is tricky. You want your code to be open-source for it's benefits (for eg, for us one benefit is building trust with people working with sensitive data). But, the history of open-source tools is full of tools that another company just started reselling without doing any of the work (sentry, mongodb etc). So, you need to find a balance. AGPLv3 strikes the right balance for us.
To your second point - completely agree that most users would expect these feature from their IDEs today. But, only two IDEs support Jupyter Notebooks: VSCode and PyCharm. You can certainly use them for notebook work but most AI extensions written for VSCode wouldn't be optimized for notebook work (for eg, GH Copilot apparently has difficulty completing code across different cells as per a friend). Secondly, to your point, this is just a start - we're going to be building a lot more Data Analysis specific features that don't exist in any IDE. I think there's a decent space for a tool a like this.
Our goal is to make a modern literate programming tool. On a surface level, a tool like that would end up looking very similar to Jupyter, though with better features. We've mentioned some things we'd like to have in this final tool in our README and also in the post above.
Our first thought was to make a tool from scratch. The challenge was, it's very hard to get people to switch and so, we had to go where people already are - that meant Jupyter.
We could've made this one feature an extension with some difficulty (in-fact, our early experiments, we started by making an extension). It would have some downsides - we wouldn't have granular control over certain core Jupyter behaviours like we do right now (for eg, we wanted to allow creating hidden folders to store some files). But we probably could have made a 95% working version of Pretzel work as a jupyter extension.
The bigger reason we chose to fork was because down the line, we want to completely change the code execution model to being DAG based to allow for reproducible notebooks (similar to https://plutojl.org/ for eg). Similarly, we want to completely remove Codemirror and replace it with Monaco (the core editor engine in VSCode) to provide a more IDE like experience in Jupyter. These things simply couldn't have been done as extensions.
Meanwhile, we also found a better speed/quality tradeoff with Codestral (since it has a fill-in-the-middle version, unlike a general LLM) so we decided to go with Codestral. This is inspired by continue.dev using Codestral for tab completion :)
[1] https://github.com/github/copilot.vim [2] https://zed.dev/blog/copilot
We pull all of your config from the ~/.jupyter folder so you should be able to switch between Jupyter and Pretzel from different python environments (though you might see some warnings)
The first time you ride in one, it feels truly sci-fi. But within 5 minutes, you're almost bored of it - that's how good it is. If I had to choose between an Uber of questionable cleanliness and driver temperament and a Waymo with a slightly longer wait and slightly more fare, I'd choose the Waymo every time.
(I have no affiliation with Waymo, Google or any related industry - it's just an amazing service!)