anyway i posted the new chakra contamination chapter
(it's very explicit pornography)
also god i love the temerity of being like 'warning p3d0philia, in3st, rap3' like oh okay people might have blocked certain words but this post is _really_ important so i'm gonna try to circumvent that, so people really definitely see my very important discourse post
the `Maybe a` should actually probably be like, `Writer a ()` but since i never use writer monads i didn't really think of it. there's another thing in the event handler that's like the perfect case for using reader monads, just... who actually uses reader/writer monads.
so these are my event handlers now & the second constructor is this thing i've gotten into the habit of doing that i refer to as "quantified existential fun"
i mean i guess they're both quantified existential fun i just really enjoy the aspect of it where you can stuff paired producer & consumer types into a type constructor & as long as no trace of the types escapes directly then you can clap your hands and make them vanish. very useful for heterogenous stuff like, event handler state.
not pictured: everything being 8 pixels above where it ought to be; the geometry being shattered apart into two overlapping triangles for each character; nothing being rendered at all b/c i got the triangle order wrong so it's all back faces.
sometimes you get fancy nice-looking screenshots but most of the time you get this
that it's literally anything other than the clear color represents an enormous success
yeah after redoing things w/ some handmade quantified existential stuff i feel like that's a much easier handle on how to do event stuff. i might bring back yampa/dunai if i get this thing to the point of needing physics, since its timing+integration code could be interesting there, but just for menu stuff, yeah, i'm gonna just do something simpler
like tbh i still haven't found a good answer for "what's the idiomatic FRP way to open and close a menu" which kind of suggests to me that the whole thing is not a good idea to use for input handling
i think in practice you wouldn't want to just blindly merge two event processors tho; you'd actually want to run one, see if it generated a response, and then only if it didn't run the other one. but still,
also FRP seems incredibly ill-suited to real-time programs-with-input ughh
maybe i'll just hack together something using reactivebanana since nothing else seems better + that's the library i know how to use mostly
definitely frustrated w/ code right now. admittedly half of that is just like, yeah you gotta write a simple shader, and set up your gl context, and write some file-loading code and image-loading code&c&c
i really gotta rig up a version of my haskell code that's actually like, robust to arbitrary rendering. just slice away all of the super complex labyrinths i make for myself so i can easily render some stuff
or i guess accept using webgl, but, probably not that
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!