I feel like there is some cause to list CS degrees and their position on Unix and Linux. awesome-linux-cs repo?

What languages are you wanting to use, the combination between toolkit and language can make a big difference to your experience.

There are a lot of interesting options out there that aren't top of people's minds too. For instance Lazarus, and Flutter. Both can do cross platform.

For another conversation I need some evidence of that, where did you find it?

This sounds like FUD to me. If it were it would be acquired pretty quickly.

Using btrfs with subvolumes to mount different disks in different locations. To maintain an "OS" disk and "what really matters" disk.

I have never tired Daisy Chaining but I hear it exists on some of the models not sure about the specific one I linked.

Played 4 first, if you do that you really notice the retrocons etc. I figure in order probably works best.

Not sure 12 hours is enough time for me to grab much. Perhaps my backlog.

The busybox one seems great as it comes with shells. php looks like it would add some issues.

Personally since I use go, I would create a go embedded app, which I would make a deb, rpm, and a dockerfile using "goreleaser"

package main

import (
	"embed"
	"net/http"
)

//go:embed static/*
var content embed.FS

func main() {
	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		// Serve index.html as the default page
		http.ServeContent(w, r, "index.html", nil, content)
	})

	// Serve static files
	http.Handle("/static/", http.StripPrefix("/static/", http.FileServer(http.FS(content))))

	// Start the server
	http.ListenAndServe(":8080", nil)
}

Would be all the code but allows for expansion later. However the image goreleaser builds doesn't come with busybox on it so you can't docker exec into it. https://goreleaser.com/customization/docker/

Most of the other options including the PHP one seem to include a scripting language or a bunch of other system tools etc. I think that's overkill

Don't let your guard down but at some point trust and risk consideration is required for most systems to work. If you're after solutions; you could run your own node in the cloud and federate it.

Limited time to build something so you have to pick based on a couple factors, often largest % of users.

Definitely related to the fall of usenet. The fact that it's ungoverned and standard, but the immediately obvious fix is not a situation people want either.