python-b5

I've been working on an XML parser of my own recently and, to be honest, as long as you're fine with a non-validating parser (which are still compliant), it's really not that bad. You have to parse DTDs, but you don't need to actually _do_ anything with them. Namespaces are annoying but they're not in the main spec. CDATA sections aren't all that useful, but they're easy to parse. As far as I'm aware, parsers don't actually need to handle xml:lang/xml:space/etc themselves - they're for use by applications using the parser. Really the only thing that's been particularly frustrating for me is entity expansion.

If you want to support the wider XML ecosystem, with all the complex auxiliary standards, then yes, it's a lot of work, but the language itself isn't that awful to parse. It's a little messy, but I appreciate it at least being well-specified, which JSON is absolutely not.

I dislike the ellipsis character on its own merits, honestly. Too scrunched-up, I think - ellipses in print are usually much wider, which looks better to me, and three periods approximates that more closely than the Unicode ellipsis.

Using LF on Windows is really not difficult. Any text editor actually worth using supports both types of line endings - even Notepad has handled this correctly for years now, from what I remember. I've never been caused any inconvenience as a Windows user by files with LF endings. I never use CRLF if I can avoid it; I only will if working on a codebase that already uses it throughout.

DragonRuby seems interesting, but being a paid product immediately rules it out for me. I've been working on my own similar, smaller framework, which is more work, but I believe it's valuable not to depend on a for-profit company for your work, if at all possible.

Also, the attitude much of the wiki / promotional pages are written in for that framework runs me the wrong way for some reason. "Unity and GameMaker rot your brain"... are you kidding me? No they don't. You're still writing real code and solving real problems. They just have more systems in place you have to work within. I don't like the self-righteous attitude. It's fair to not want to go open source if that's your preference, but don't act like people who don't want to use closed-source software where possible are being unreasonable. I also don't see how what is effectively a Ruby wrapper for SDL3 is such an immensely complicated piece of engineering that it needs to cost as much as they're charging for it.

Using AI makes you an artist about as much as commissioning someone else to make art for you does. Sure, you provided the description of what needed to be done, and likely gave some input along the way, but the real work was done by someone else. There are faster iteration times with AI, but you are still not the one making the art. That is what differentiates generative models from other kinds of tools.