Crafting Interpreters
bocker
Crafting Interpreters | bocker | |
---|---|---|
45 | 37 | |
8,166 | 11,092 | |
- | - | |
0.0 | 0.0 | |
28 days ago | over 6 years ago | |
HTML | Shell | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
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.
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...
-
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.
-
A roadmap to design programming languages
Crafting Interpreters is a fun primer on language design. It has a complete roadmap to build a fairly simple language, twice. There are some topics it won't touch on, like static type systems, but it provides a great introduction so that you can start tinkering and learn by doing.
bocker
-
Show HN: Bocker-compose, the missing layer to Docker-compose
A (joke?) one-liner I came up with while thinking about solutions to centralized container management across multiple SSH hosts. Shame on me.
The name is inspired by bocker [0], albeit this doesn't re-implement docker-compose in bash, I found it to be fitting enough.
I'd love to see someone come up with a smarter and/or shorter way to do this.
[0] https://github.com/p8952/bocker
-
Barco: Linux Containers from Scratch in C
When I did a talk about docker I also wanted to show a bit of what it does under the hood without going through all the layers and without too much details. This ~120 lines of shell script is really good in providing just an intro into what's needed for containers: https://github.com/p8952/bocker/blob/master/bocker
- Build Your Own Docker with Linux Namespaces, Cgroups, and Chroot
-
Latest Zen Kernel......
i tried it and like the concnpt, but until it can be launched via a systemd userspace service (without previously manually booting it) among other problems i will keep using docker (or bocker)
-
The Staff Engineer's Path – Book Review
> But you couldn't reimplement podman in a few hundred lines of code.
You don't even need a few hundred: https://github.com/p8952/bocker
And then there's 'dokku' which IIRC, started as a bash version of Heroku.
> Not all ideas have the same quality.
They really do. I've heard all kinds of things in my career, but almost none I would want to dedicate a portion of my life building. Not because they are bad ideas or won't work, but because of the person with the idea or it just didn't interest me. Those people went on to be moderately successful (like hundreds of millions worth) but I'm glad I wasn't on that ride.
-
“Implement DNS in a Weekend”
Bocker is in this same category...docker clone in bash that's helpful in seeing what's really happening underneath with nsenter, namespaces, network bridging, cgroups, etc.
https://github.com/p8952/bocker
-
Ask HN: What is the best source to learn Docker in 2023?
Docker implemented in around 100 lines of bash: https://github.com/p8952/bocker
This is the most mindblowing example for enterprise security teams that think Docker is a new threat on a single tenant Linux host.
No, buddies, all this stuff is already there. If you were fine with your visibility before*, you're still fine. Go find a real problem while we play with our developer dopamine.
* NARRATOR: They shouldn't have been.
-
Containers are chroot with a Marketing Budget
Bocker[1] does a reasonably good job of showing the value of Docker was mostly in Docker hub.
[1] https://github.com/p8952/bocker
There is a cool project I've seen called "bocker" (https://github.com/p8952/bocker) which is something of a proof of concept of implementing Docker with bash, which speaks a bit to how Docker is indeed in many ways an amalgam of lower level primitives (such as chroot as you mentioned). Pretty neat!
- bocker: Docker implemented in around 100 lines of bash
What are some alternatives?
git-internals-pdf - PDF on Git Internals
whalebrew - Homebrew, but with Docker images
You-Dont-Know-JS - A book series on JavaScript. @YDKJS on twitter.
s6-overlay - s6 overlay for containers (includes execline, s6-linux-utils & a custom init)
tinyrenderer - A brief computer graphics / rendering course
garden - Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching
paip-lisp - Lisp code for the textbook "Paradigms of Artificial Intelligence Programming"
distroless - 🥑 Language focused docker images, minus the operating system.
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
dockerfiles - Various Dockerfiles I use on the desktop and on servers.
30-days-of-elixir - A walk through the Elixir language in 30 exercises.
cloc - cloc counts blank lines, comment lines, and physical lines of source code in many programming languages.