I've been hacking some rough IRCv3 support into a twisted.words.irc implementation recently and, having looked at the specs for the extra tags and things, I think we can all agree that MS Comic Chat was ahead of its time and deserved to be the winning protocol

#irc #twistedPython #MSComicChat

#tnt #gamedev #devlog I guess it’s take most of a week to get to a place that looks exactly where I was before, but the #wasm port is now working quite well in the browser (ignoring a bunch of interface issues someone who knows browsers could fix in a few minutes). The entire application has been turned inside out to make it asynchronous.

On the terminal it runs under #tokio and that conversion was my first exposure to async on #Rust. I did a lot of async coding for #TwistedPython back before python or many other languages had support for asynchronous models. Boy are things ever a lot nicer nowadays.

On the browser, everything just runs under #yew. Almost everything Just Worked. The only thing I had to do was figure out how to get time support in futures, which was just a matter of adding a crate I think. It’s so amazing that we can use the same language in a kernel or device driver and the browser. Finally.

The conversion was relatively painless! I didn’t have to touch any of the code that implements game content, so that’s not too shabby. Game content code can now do things like get a keypress from the user, where before all interaction had to be via the text parser. So this allows for things like menus and dialog trees. And maybe a fancy Encounter interface, which is my next major project.

The web port doesn’t have some basic UI features like backspace but IFAICT it’s completely proven out and smooth sailing from here. I’m really excited that I’ll be able to actually allow people to play this thing now, on almost any modern device.

I’m also still very interested in porting to the #6502 but after 1.0, if that ever arrives.