>>5
>>3 here.
I would like to write a game and I'm currently using SDL components. I'm realizing that while it's fairly nicely integrated in the code, that's a lot of extra libraries for some minimalistic functionality that I'll be using. I would prefer to write my own specifically tailored library and use that. I think it looks like ass to have SDL_mixer, SDL_image, SDL, etc. in the directory.
I don't exactly require cross-platform support, although I do want to be able to expand to this eventually.
I don't think I'll be using much in the way of text, and regardless, I should be able to use ASCII on unicode environments. I don't think the text I'm using will need to be localized, because it'll be almost 100% numbers.
Plus, accounting for unicode in all my API calls and stuff requires pain-in-the-ass workarounds because Sepples is *NOT* designed for anything after 1980, including threading, modern networking, and unicode support.
I imagine that most of the questions you posed were relevant to
>>1, but I was asking a serious question.