os01
papers-we-love
os01 | papers-we-love | |
---|---|---|
10 | 69 | |
11,493 | 83,584 | |
- | 1.1% | |
0.0 | 3.2 | |
about 1 month ago | 11 days ago | |
TeX | Shell | |
- | - |
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.
os01
-
The Top 10 GitHub Repositories Making Waves 🌊📊
Write an OS from scratch
-
Write your own OS - starting from the bootloader
(Here is the link - didn't quite get the image/link combo right in the original post!). I'm writing a series of posts about coding your own operating system. After reading Operating Systems: From 0 to 1 I found that some of the code does not work, so this first post walks you through writing a bootloader similar to that of chapter 7. It also adds some context that I would have found useful when I originally read the book, such as how 16-bit real mode works and some assembly programming information. I'm hoping to take a different approach to posts in the series by borrowing pieces of other operating systems and discussing how they are implemented in an effort to keep things simple and focus on fundamentals (even Linus started out with a detailed reading of MINIX).
Starting a series about writing your own operating system. After reading Operating Systems: From 0 to 1 I found that some of the code does not work, so this first post walks you through writing a bootloader similar to that of chapter 7. I'm hoping to take a different approach to posts in the series by borrowing pieces of other operating systems (even Linus started out with a detailed reading of MINIX).
-
Kernel (OS Kernel Book)
Very quickly skimming through the various chapters, it appears that this is gentle introduction as attention has been made on clear and verbose explanations, supplemented with diagrams. Comparable other "courses" could be osdev101 [1] and "Writing an operating system from scratch" [2].
[1] https://github.com/tuhdo/os01/blob/master/Operating_Systems_...
[2] https://www.cs.bham.ac.uk/~exr/lectures/opsys/10_11/lectures...
- Practice-Oriented Books on OS Development?
- How to learn C intensively?
-
Making projects or reading source code for learning,
You need to be aware of how it works on a hardware level but probably not an expert, for a better explanation see: https://github.com/tuhdo/os01
- Resources to learn OS programming in C
- Operating Systems: From 0 to 1: Write an operating system from scratch
-
The Road to My Ultimate Training System
Operating Systems from 0 to 1
papers-we-love
-
The Top 10 GitHub Repositories Making Waves 🌊📊
Papers We Love (PWL) is a community built around reading, discussing and learning more about academic computer science papers. This repository serves as a directory of some of the best papers the community can find, bringing together documents scattered across the web. You can also visit the Papers We Love site for more info.
- What led you to use Linux as your daily driver?
-
We have used too many levels of abstractions and now the future looks bleak
You might find the paper Out of the Tar Pit interesting if you haven't already read it: https://github.com/papers-we-love/papers-we-love/blob/main/d...
The ideas and approaches you talk about evoked some of the concepts from that paper for me. It talks a lot about separating accidental complexity and infrastructure so you can focus only on what is essential to define your solutions.
- Out Of The Tar Pit (2006) [pdf]
-
John McCarthy’s collection of numerical facts for use in elisp programs
Sure he was expecting a practical language and was designing one. Lisp was from day zero a project to implement a real programming language for a computer.
Earlier he experimented with IPL and also list processing programming on Fortran. The plan was to implement a Lisp compiler. At first the Lisp code McCarthy was experimenting with, was manually translated to machine code.
Then came up the idea to use EVAL as a base for an interpreter, which was implemented by manually translating the Lisp code to machine language. Around 1962 then a compiler followed.
https://github.com/papers-we-love/papers-we-love/blob/main/c...
-
Python: Just Write SQL
I'm in a 4th camp: we should be writing our applications against a relational data model and _not_ marshaling query results into and out of Objects at all.
Elaborations on this approach:
- https://github.com/papers-we-love/papers-we-love/blob/main/d...
- https://riffle.systems/essays/prelude/
- CS Journals and Magazines?
-
Ask HN: Incremental View Maintenance for SQLite?
The short ask: Anyone know of any projects that bring incremental view maintenance to SQLite?
The why:
Applications are usually read heavy. It is a sad state of affairs that, for these kinds of apps, we don't put more work on the write path to allow reads to benefit.
Would the whole No-SQL movement ever even have been a thing if relational databases had great support for materialized views that updated incrementally? I'd like to think not.
And more context:
I'm working to push the state of "functional relational programming" [1], [2] further forward. Materialized views with incremental updates are key to this. Bringing them to SQLite so they can be leveraged one the frontend would solve this whole quagmire of "state management libraries." I've been solving the data-sync problem in SQLite (https://vlcn.io/) and this piece is one of the next logical steps.
If nobody knows of an existing solution, would love to collaborate with someone on creating it.
[1] - https://github.com/papers-we-love/papers-we-love/blob/main/design/out-of-the-tar-pit.pdf
-
Good papers for high school students?
Here is a great Repo on GitHub named paers-we-love. You will surely find some great papers there and also some good other resources. Hope this helps.
-
I think Zig is hard but worth it
However, f and g are interchangeable anywhere else (this is not actually true because their addresses can be obtained and compared; showing that a C-like language retains its referential transparency despite the existence of so-called l-values was the point of what I think is the first paper to introduce the notion referential transparency to the study of programming languages: https://github.com/papers-we-love/papers-we-love/blob/main/l...)
What are some alternatives?
os-tutorial - How to create an OS from scratch
Crafting Interpreters - Repository for the book "Crafting Interpreters"
book-pr - Pull Requests and Code Review: Best Practices for Developers, from Junior to Team Lead.
Flowgorithm-macOS - Flowgorithm for Mac OS
esProc - esProc SPL is a scripting language for data processing, with well-designed rich library functions and powerful syntax, which can be executed in a Java program through JDBC interface and computing independently.
elm-architecture-tutorial - How to create modular Elm code that scales nicely with your app
wtfjs - 🤪 A list of funny and tricky JavaScript examples
clojure-style-guide - A community coding style guide for the Clojure programming language
traducao_como_jogar_go - Tradução do livro "How to Play Go: A Concise Introduction", por Richard Bozulich e James Davies, da editora Kiseido
git-internals-pdf - PDF on Git Internals
sample-os - A sample OS as demonstrated in the book Operating System: From 0 to 1
salsa - A generic framework for on-demand, incrementalized computation. Inspired by adapton, glimmer, and rustc's query system.