Or complete clients, doesn't even need to be great but incorporating all features would be nice.
Some people who are self studying Structure and Interpretation of Computer Programs have been using a discord server to assist each other as needed. I realize that there are a number of people using Lemmy whi are very opposed to using discord over other options, but I don't know of any other sustained forums focused on this book.
That's an entry point into programming that's not for everyone. It seems like the poster is looking for something more hands on and pragmatic rather than technical and academic.
An author of the original book, Allen B. Downey, has released a third edition if his updates that is also available online at no cost and in Allen B. Downey's words:
The book is now entirely in Jupyter notebooks, so you can read the text, run the code, and work on the exercises – all in one place. Using the links below, you can run the notebooks on Colab, so you don’t have to install anything to get started.
The text is substantially revised and a few chapters have been reordered. There are more exercises now, and I think a lot of them are better.
It's interesting to see how the same source material has grown into two differently maintained and similar resources.
Pixi is more than a drop in replacement for Conda. Pixi being able to replace Conda and do everything that uv does (Pixi has incorporated uv into it's tools) seems to make it a more complete toolset than uv alone.
There seems to be mixed reactions to this suggestion. I don't know enough to understand why.
Why is there often no discussion or mention of Pixi along with uv in conversations about Python tooling? Is it because uv has a lot of VC money to get attention while Pixi doesn't?
Or The Odin Project if you don't want to cover Python in the curriculum and just stick to JavaScript.
https://www.theodinproject.com/
(The Odin Project also has an option for Ruby along with JavaScript)
A git commit is a snapshot. The node-based tree structure is an artifact of recording pointers to other snapshots and labeling snapshots with a branch name.
@ericjmorey
@programming.dev