git-from-the-bottom-up
Crafting Interpreters
Our great sponsors
git-from-the-bottom-up | Crafting Interpreters | |
---|---|---|
32 | 45 | |
801 | 7,995 | |
- | - | |
1.8 | 0.0 | |
7 months ago | 5 days ago | |
HTML | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
git-from-the-bottom-up
- Git from the Bottom Up
-
git-appraise – Distributed Code Review for Git
Very tangential:
Gerrit also stores some of its configs in a git repo. I was setting up a new instance, but couldn't get Admin permissions because the way my auth front-end didn't play well with the docker image's assumptions.
Gerrit already does a lot of its work via non-standard references. For example, you don't push to a branch, `refs/branches/foo`, you push to a separate `refs/for/foo` namespace that creates the review.
Similarly, Group config is stored in the All-Users git repo [1], but in references created after a UUID, in `refs/groups/UU/UUID`.
I ended up having a to exercise the plumbiest of plumbing commands [2] to create a new commit from scratch (from a tree, from the index, from blobs), to update the group ref to add myself to the Administrators group (this, of course, requires a local shell and permissions on the Gerrit host). It was a great way to exercise what I had learned in Git from the Bottom Up [3]
[1] https://gerrit-review.googlesource.com/Documentation/config-...
[2] https://git-scm.com/book/en/v2/Git-Internals-Git-Objects
- Good git course and/or where to practice real life scenarios?
-
Git-SIM: Visually simulate Git operations in your own repos with a single termi
You won't have to put your entire life on break in order to understand the fundamentals of git and why it works the way it works. Going through https://jwiegley.github.io/git-from-the-bottom-up/ and really understanding the material will take you a couple of hours at max, but will save you a lot of time in the future.
Wanting to understand things before using them is hardly elitism, not sure why you would think that.
Just like you probably don't want to fix bugs without understand the cause, it's hard to use a tool correctly unless you know how the tool works.
-
Git book recommendations?
If that's too dense, read https://jwiegley.github.io/git-from-the-bottom-up/, which is basically the same as chapter 10 at a slower pace.
-
Ask HN: Do you recall any book or course that made a topic finally click?
Git From The Bottom Up : https://jwiegley.github.io/git-from-the-bottom-up/
-
Does anyone know of a good yet simple Git overview?
here's one tutorial https://jwiegley.github.io/git-from-the-bottom-up/ from bottom to top, it explains the building blocks then the operations, it might help (again, depending on your brain)
-
Is it really that much easy? Because in the beginning I was a lot scared of it.
I can recommend https://jwiegley.github.io/git-from-the-bottom-up/ and of course https://git-scm.com/docs/gittutorial (also gittutorial-2).
-
Git In Two Minutes (updated after 8 years)
It's not a single digit minute read, but to me "Git from the Bottom Up" was what really made me understand git a long time ago.
https://jwiegley.github.io/git-from-the-bottom-up/
git's the kind of tool where understanding how your commands operate on the underlying data structures will probably make it a lot easier to use efficiently. (And they're beautifully simple despite how powerful and flexible they are)
As a tool you might be using for hours per week for a few more decades, it's worth the investment going beyond the "in x minutes". I tend to provide both to juniors.
Obligatory: https://xkcd.com/1597/
Crafting Interpreters
- Crafting Interpreters
-
The Top 10 GitHub Repositories Making Waves 🌊📊
Build an Interpreter (Chapter 14 on is written in C)
-
Writing a Debugger from Scratch: Breakpoints
I’m guessing you’ll have to work with the scopes in the resolver:
https://github.com/munificent/craftinginterpreters/blob/mast...
I was asking this myself this while reading the book "Crafting Interpreters". I posted a few resources I found on an issue about implementing debuggers [] although honestly I still haven't gotten down to read all of them (or to implement a debugger! :-/).
--
: https://github.com/munificent/craftinginterpreters/issues/92...
-
loxcraft: a compiler, language server, and online playground for the Lox programming language
Better open an issue/request wiki edit at https://github.com/munificent/craftinginterpreters/wiki/Lox-implementations
- Gigachad Ken Thomson.
-
Show HN: Yaksha Programming Language
I'm late to the party, but I want to say thank you for sharing this. It's inspiring to look at how much you've built and (hopefully) enjoyed the process of building! I'm loving everything -- your site, your language design, your docs, your builtin libraries, your dev tools. Beyond impressive. People like you are the ones who make HN one of my best places on the internet.
For context on where I'm coming from, about two weeks ago I picked up Crafting Interpreters [1] for fun. I'm finding your clear-yet-concise Compiler internals [2] to be particularly compelling reading, and jumping back and forth between those "how this all works" docs and the live example of this language you actually built do a WASM-compiled tree-blowing-in-the-wind animation is just... just wow. So freaking cool!
I also enjoyed reading the comment thread that inspired you to start on Yaksha and seeing how this project has a wholesome start as inspiration-by-programming-hero. I hope you recognize that a few years later you've now ascended from inspiree to inspirer. I also hope you're still having tons of fun building out Yaksha!
[1] https://www.craftinginterpreters.com/
[2] https://yakshalang.github.io/documentation.html#compiler-int...
- Keeping track of returned and break-ed values between code blocks
-
How do you start your own programming language?
There are books which will talk you through the process. Crafting Interpreters is highly spoken of; I used Writing an Interpreter in Go, because I like Go. Then there's Compilers: Principles, Techniques, and Tools (the "Dragon Book"). This is considered heavy, but a classic, it's been around since '86.
-
Designing a new language
I cannot recommend Crafting Interpreters by Robert Nystrom enough, it covers a lot of the stuff you need to know, completely for free.
What are some alternatives?
git-internals-pdf - PDF on Git Internals
You-Dont-Know-JS - A book series on JavaScript. @YDKJS on twitter.
tinyrenderer - A brief computer graphics / rendering course
paip-lisp - Lisp code for the textbook "Paradigms of Artificial Intelligence Programming"
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
30-days-of-elixir - A walk through the Elixir language in 30 exercises.
clojure-style-guide - A community coding style guide for the Clojure programming language
project-based-learning - Curated list of project-based tutorials
papers-we-love - Papers from the computer science community to read and discuss.
web-dev-golang-anti-textbook - Learn how to write webapps without a framework in Go.
pyright-python - Python command line wrapper for pyright, a static type checker
lisp - Toy Lisp 1.5 interpreter