For personal projects: GIT barebone repositories + Wireguard to access them from all my devices.
OSS work is mirrored to Codeberg and SourceHut. For actions I try to make sure that local builds, and cross compilation to Windows, macOS, armhf and arm64, is always working to not soley depend on Github Actions.
That was a nice read. I didn't know there were vector graphics in these systems. Found Canadian description of the Telidon "Picture Description Instructions (PDI)"
It is an interesting project, but I'm sceptical. Veilid appears to be focused on their implementation in Rust, not so much as reference implementation but as the thing itself. I was hoping for a W3C like definition of a standard, not "bound" to their implementation or Cap'n Proto.
Same here, every system is different, but my main desktop Arch installation is kicking since 6 years now with absolute minimal maintenance issues. Perhaps 1-2 times per year maximum things need to be fixed manually in super rare cases.
I've recently compiled my JSON parser with Borland Turbo C compiler (from 1989) on FreeDOS. It feels good to see the code builds with compilers covering 34 years. ANSI C is still remarkable.
Hi HN, here is my take for a minimal structured format. It doesn't specify anything other than the structure, and leaves the data type specifics to the application.