collapseos VS single_file_libs

Something like this is probably a lot more realistic than (as fast) "integrated circuits at home" : http://collapseos.org/

http://collapseos.org/

I know the point of it isn't to run on new hardware, but this would be a way to learn it on a stable platform without having to worry about dealing with constant problems from old hardware before trying to implement it on said.

There is something called Collapse OS I read about here on HN:

http://collapseos.org/

I myself am a collector of old devices, having raised three kids plus being a web dev. Hate throwing them away too I was just think about this today could I extract the CPUs or RAM or something to reuse rather than destory for the metals. I'd like to learn more hardware but no time.

Some hope for Colapse OS [1] perhaps?

[1] http://collapseos.org

http://collapseos.org/

Here is a quick guide to the science for those with the brain worms:

Maybe start with sufficient support for a simple OS that allows you to edit and compile programs. Something like FreeDOS or CollapseOs. Once you have that working you can extend it.

During collapse we'll all be using Dusk OS and post collapse we'll be using cobbled together rugged computers running on Collapse OS. I imagine at that point we can probably put the sub name to a vote. Maybe "r/ordinarylife".

Not Linux....but you could just install Kolibri OS for a very light desktop or consider CollapseOS and DuskOS....think Dusk should run bare metal on now and won't be too bloated, but there's always CollapseOS if you prefer to keep things light

Yep: https://github.com/nothings/single_file_libs

Also sometimes I use only header (.h) with all functions included wrapped by #ifndef and #endif. When I use these? for code that I always reuse to simplify things and some data stucture handling (to implement dynamic arrays). A good example list of these (not mine) are https://github.com/nothings/single_file_libs

Also, there are many libraries that are much bigger (little list I found) but are implemented in a single header file.

If others have a similiar problem, I found a great github page that has lots of single header libraries, including data structures.

> Like, why don't we just let projects be "done"? Things don't need to be maintained and updated for eternity.

This is generally why I opt for "single-file" libraries that do one simple task well. The smaller the library, the more likely it is "done". For example, do I want some insanely complex image library that handles every file format under the sun, or do I just want some basic one that allows me to output a simple JPEG?

I often find myself referring to "single_file_libs" repository: https://github.com/nothings/single_file_libs

Looking at the open issues, it doesn't appear to be actively maintained but it's still an incredibly good resource for "completed" projects.

Steamworks is the easy option, but if you're programming-savvy you could also use a networking library (some lists for C and C++: 1 2 3) to accomplish the same thing.

Have a look at these. https://github.com/nothings/single_file_libs#geometry-file