-
toaruos
Discontinued A completely-from-scratch hobby operating system: bootloader, kernel, drivers, C library, and userspace including a composited graphical UI, dynamic linker, syntax-highlighting text editor, network stack, etc.
-
toaru-nih
Discontinued NOTICE: The ToaruOS-NIH Project has been MERGED UPSTREAM. This repository is now archived.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
From an old FAQ page[1] for TauruOS:
> I wrote ToaruOS at a time when I was much more competent at C than C++. I still think that's true. At this point, the effort of rewriting datastructures to make use of C++ functionality would not be a good use of time - and writing userspace code in C++ in ToaruOS-NIH is not yet possible as I have yet to get a C++ standard library set up.
1: https://github.com/klange/toaru-nih/wiki/FAQs
> Plus C++ standard library can't be used anyway and auto pointers aren't really that much of a concern at the kernel level
https://github.com/microsoft/wil
"Ah, but that isn't used on the Windows kernel" would be the expected reply, well
https://community.osr.com/discussion/291326/the-new-wil-libr...
"Microsoft's toolchain does not ship a copy of the STL that works in kernel mode. Partly this is because the kernel's CRT doesn't support C++ exceptions. (And partly this is because I/O is wildly different in kernel, so you'd have to rewrite the implementation of all the I/O libraries.)
But for kernel developers, wil ships a subset of an STL implementation. To avoid conflicting with the real STL, it's available under the wistd namespace. The rule of thumb is that wistd::foo is a drop-in replacement for std::foo."