 Thinking of writing moderately complex/useful software on top of CHIP-8. Reasons not to: - It’s not accessible. - Bad specification, everyone has their own slightly incompatible implementation (the dialect comparison page lists 12 dialects.) - It’s restricted in graphic abilities, hard to make text-heavy apps in it. I mean, there are 4x4 fonts, but the screen is too small nonetheless. So I guess I’ll stay with HTML after all. 8 comments
@neauoire anything and everything really. But one example might be a hypertext-ish interactive book. Would be really fun to distribute by blog posts as CHIP-8 executables 🤩 But I’m still searching for a reliable and portable base for computation now that I abandoned Brainfuck a year ago. That’s why there’s this huge range of options I’m considering. I guess it’s somewhat similar to your search of computation basis with uxn?  @aartaka CHIP-8 is famously bad at displaying text, and HTML is not a virtual machine at all. Do you mean you're looking for a kind of markdown format to share your posts in? Or do you consider HTML as a base for computation somewhat? I don't think HTML addresses what uxn is designed to address, so I think we might be looking for different things. Have you looked at the SECD or warren abstract machines? @neauoire I’ve been confusing I guess 😅 What I mean by similarity of goals is that we both are looking for something reliable and portable to base our software off. In this sense, HTML (and the surrounding technology, however wary I am of JavaScript) is a perfect portability layer for me. Regarding the interactive/hypertext blogs though, I am indeed in search of a good format for my posts. I’m settled on HTML for now, but that might change. See also https://aartaka.me/hypertext  @aartaka I got around to checking out your defense of html, and it doesn't really make sense to me. Why will the minor differences in markdown implementations matter more than relying on Google to render html in the long term? Why is the browser less likely to die than Obsidian? @neauoire @akkartik @aartaka that said, Markdown dialect incompatibilities are a worse problem than different versions of browsers. and there’s the perhaps minor point that markdown has a much more direct dependency on html and the precise ways it renders in a browser than most people realise, even setting aside that the standard requires that a markdown dialect literally support all of html inline |
Gregory's Server
@aartaka wow, what sort of project did you have in mind that had to be either one of these totally opposite platforms?