os01
STL
os01 | STL | |
---|---|---|
10 | 154 | |
11,493 | 9,763 | |
- | 1.1% | |
0.0 | 9.7 | |
about 1 month ago | 1 day ago | |
TeX | C++ | |
- | 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.
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
STL
-
Show HN: Logfmtxx – Header only C++23 structured logging library using logfmt
Again, they are barely functional.
MSVC chokes on many standard-defined constructs: https://github.com/microsoft/STL/issues/1694
clang does not claim to be "mostly usable" at all - most papers are not implemented: https://clang.llvm.org/cxx_status.html#cxx20
And gcc will only start ot be usable with CMake when version 14 is released - that has not happened yet.
And, as I mentioned before, IDE support is either buggy (Visual Studio) or non-existing (any other IDE/OS). So you're off to writing in a text editor and hoping your compiler works to a somewhat usable degree. Yes, at some point people should start using modules, I agree, but to advise library maintainers to ship modularized code... the tooling just isn't there yet.
I mean, the GitHub issue is Microsoft trying to ship their standard library modularized, they employ some of the most capable folks on the planet and pay them big money to get that done, while metaphorically sitting next to the Microsoft compiler devs, and they barely, barely get it done (with bugs, as they themselves mention). This is too much for most other library maintainers.
-
Cpp2 and cppfront – An experimental 'C++ syntax 2' and its first compiler
Notice that there are in practice three distinct implementations of the C++ standard library. They're all awful to read though, here's Microsoft's std::vector https://github.com/microsoft/STL/blob/main/stl/inc/vector
However you're being slightly unfair because Rust's Vec is just defined (opaquely) as a RawVec plus a length value, so let's link RawVec, https://doc.rust-lang.org/src/alloc/raw_vec.rs.html -- RawVec is the part responsible for the messy problem of how to actually implement the growable array type.
Still, the existence of three C++ libraries with slightly different (or sometimes hugely different) quality of implementation means good C++ code can't depend on much beyond what the ISO document promises, and yet it must guard against the nonsense inflicted by all three and by lacks of the larger language. In particular everything must use the reserved prefix so that it's not smashed inadvertently by a macro, and lots of weird C++ idioms that preserve performance by sacrificing clarity of implementation are needed, even where you'd ordinarily sacrifice to get the development throughput win of everybody know what's going on. For example you'll see a lot of "pair" types bought into existence which are there to squirrel away a ZST that in C++ can't exist, using the Empty Base Optimisation. In Rust the language has ZSTs so they can just write what they meant.
- C++ Specification vs Implementation
-
C++23: Removing garbage collection support
Here is Microsoft's implementation of map in the standard library. I think of myself as a competent programmer / computer scientist. I couldn't write this: https://github.com/microsoft/STL/blob/f392449fb72d1a387ac502...
-
std::condition_variable wait for (very) long time
Be careful on Windows, the MSVC STL implementation uses the system time, so it can be badly impacted by clock adjustments: https://github.com/microsoft/STL/issues/718
-
Compiler explorer: can you use C++23 std lib modules with MSVC already?
Can you provide a link? If it affects import std;, I'd like to add it to my tracking issue.
- Learn to write production quality STL like classes
-
MSVC C++23 Update
Do you have a list of the bugs you've filed and their current status, like the one I have for the STL? I saw you mentioned 3 bugs 7 months ago, 2 of which were fixed in 17.6 and the third of which was a duplicate of an active bug ("deducing this" is known to not yet work with modules, which is why we don't define the feature-test macro to claim full support).
- C++/CLI wrap of a C++ class that includes <future> in public header
-
Has Boost lost its charm?
Yep. And look at our implementation's name: https://github.com/microsoft/STL
What are some alternatives?
os-tutorial - How to create an OS from scratch
EA Standard Template Library - EASTL stands for Electronic Arts Standard Template Library. It is an extensive and robust implementation that has an emphasis on high performance.
book-pr - Pull Requests and Code Review: Best Practices for Developers, from Junior to Team Lead.
asio - Boost.org asio module
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.
robin-hood-hashing - Fast & memory efficient hashtable based on robin hood hashing for C++11/14/17/20
wtfjs - 🤪 A list of funny and tricky JavaScript examples
tracy - Frame profiler
traducao_como_jogar_go - Tradução do livro "How to Play Go: A Concise Introduction", por Richard Bozulich e James Davies, da editora Kiseido
gcc
sample-os - A sample OS as demonstrated in the book Operating System: From 0 to 1
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.