Kit Sunny @roadriverrail@signs.codes

@M0YNG @gitea I'd likely never look at my logs, and if something went wrong, it'd likely take weeks to get around to fixing. I'm that swamped.

@avalos I'm sure the DS hacking community can help, but I know little of it. The original NES on an emulator is a great target though because the hardware is well known and quite well documented. I even have a set of instructional labs available to help people learn the platform. And the 6502 is an easy but iconic processor used in multiple 80s PCs and still sees use today.

@avalos Incidentally, if you're looking for a great way to get your feet wet in bare metal coding, have you considered writing your own Nintendo game from scratch? It's a great way to learn about hardware and about writing assembly language.

@neauoire Do go on!

@M0YNG @gitea Right...this is the sort of remark that makes me shy away from self-hosting. I don't have time to keep up with my own maintenance needs like that.

@hankg Yeah, I know a lot of people use and like Gitlab, and it's on the list I'm considering. Curious if there are advantages/costs to self-hosting there? I want to keep my maintenance overhead low but also have good longevity in my service.

So...if I'm going to migrate off GitHub, I have choices. I could self-host (on Dreamhost, my go-to provider, or maybe SDF). Or I could use something like Sourcehut. My projects aren't very big or heavy in traffic. Curious what folx on Fedi have tried and found useful.

@avalos Low level software has to be written to target the specifics of the hardware you're using. So you kinda have to learn both together as you go. Every time I write bare metal code, I have documentation on the hardware in hand while I do it. So really it works best to co-learn it.

@psf Grace knew what was up. One of the most consistently practical minds of the golden age of computers.