HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
redox-os
redox
Rust2015–2023
redox-os / redox

redox

Mirror of https://gitlab.redox-os.org/redox-os/redox

41Distinct people
47Mentions
1Explicit recommenders
16.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Mirror of https://gitlab.redox-os.org/redox-os/redox

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Author here. As steveklabnik says, I'm figuring this out as I go along, with much help from the amazing OSDev wiki: http://wiki.osdev.org/Main_Page Basically, this stuff is a…

ekidd used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:01:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year47 dated mentions

Observed mentions: 2015-10-03 12:55:39 UTC to 2023-08-30 04:00:00 UTC.

0510152015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 12 mentions; 3 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 15 mentions; 4 submissions, 11 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 10 mentions; 4 submissions, 6 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1239
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC15411
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1046
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
This repository is the Build System for Redox OS. Redox is under active development by a vibrant community, you can see the key links below: The main website for Redox OS. The Redox Book and Build Instructions. Redox Chat and Support. Patreon, Donate and Merch. Scroll down for a list of key Redox components and their repositories. Redox is an open-source operating system written in Rust, a language with focus on safety, efficiency and high performance. Redox uses a microkernel architecture, and aims to be reliable, secure, usable, correct, and free. Redox is inspired by previous operating systems, such as seL4, MINIX, Plan 9, Linux and BSD. Redox is not just a kernel, it's a full-featured operating system, providing components (file system, display server, core utilities, etc.) that together make up a functional and convenient operating system. Redox uses the COSMIC desktop apps, and provides source code compatibility with many Rust, Linux and BSD programs. More Links Book Contribute Hardware Compatibility Run Redox in a Virtual Machine or on Real Hardware Trying Out Redox Building Redox Build System Documentation Developer FAQ Chat/Discussions/Help Ecosystem Some of the key repositories on the Redox GitLab: Essential Repositories Maintainer Kernel @jackpot51 Base (essential system components and drivers) @jackpot51 RedoxFS (default filesystem) @jackpot51 relibc (C POSIX library written in Rust) @jackpot51 Ion (defauilt shell) @jackpot51 Termion (terminal library) @jackpot51 pkgutils (current package manager) @jackpot51 Orbital (display server and window manager) @jackpot51 This repo - the root of the Build System @jackpot51 @hatred_45 Redoxer (tool for easy Redox development on Linux) @jackpot51 The Redox Book @jackpot51 @hatred_45 Website @jackpot51 @hatred_45 What it looks like See Redox in Action for photos and videos.
Read the full README on GitHub

What Hacker News says

12 sources
I only took a brief look over the code to try to find what documentation is actually there, but I managed to find this https://github.com/redox-os/redox/blob/master/kernel/fs/url.... On your question of how typical a lack of system-internal documentation is in systems projects, the answer from my experience is unfortunately more common than it should be. There are a bunch of usage and design patterns that cannot be expressed regardless of the language you are using. I know very little about Rust, but I work mostly in Java, which is safer than many other languages (less flexible than interpreted or dynamic languages, less dangerous than C/C++). Even java, which has interfaces and strict typing can save you some of the more mundane unit tests and input validation code, has a bunch of design patterns on top of the core language. Projects cou
Read the rest
ld serve themselves well to document their code well to allow new contributors to look at any of the code and reasonably modify it to fix a bug or add a feature.
In Redox – A Unix-Like Operating System Written in Rust
I've been looking through some of the kernel code [1] out of curiosity, and I'm very surprised to see that most components have almost no internal documentation — minimal file and class comments, and even fewer inline comments. Is this typical of code for something as complex and central as an OS kernel? Are the developers planning to go back later and add documentation, or is the expectation that anyone who might need to work with this code will find its structure and details intuitive? [1] https://github.com/redox-os/redox/tree/master/kernel/
In Redox – A Unix-Like Operating System Written in Rust
I feel like this is a bad argument to be making. If a language's "level of suck" were based on its ability to write operating systems, then the massive boost in programmer productivity we see today from languages which sought to depart from that domain wouldn't exist. Tangential to that, I consider Rust a "fun" language compared to C++, and it is definitely capable of doing anything C++ can do[1]. By the way, Midori[2] was written in C#. Granted it had its own AOT compiler and started to diverge into a different language, but nevertheless, it was C#. I'd suggest looking through Joe Duffy's blog posts[3] as he explains it better than I could. [1] https://github.com/redox-os/redox [2] https://en.wikipedia.org/wiki/Midori_(operating_system) [3] http://joeduffyblog.com/2015/12/19/safe-native-code/
In Why C++ sucks (2016 edition)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.