Aeva [Any%] @aeva@toot.cat

I made an account on the game dev mastodon https://mastodon.gamedev.place/@aeva/99004363415565288

I'll likely mostly cross post everything between the two, but feel free to be mastofriends with either

overheard a lady explaining her adhd to her coworker and he kept butting in with "but i get distracted sometimes too and i get by fine". 🔥🔥🔥

there's an ad on the train that says:

"chiberia is coming
luckily, so are we."

i mean, i too am horny for winter, but

I'm excited for the future archeologists who will misunderstand "sarcophagus" and die from the wrath of the gods we created #morbidmonday

I think after work I'll have a look at what the state of real-time 3d is in the python ecosystem these days.

If the niche isn't already well served, this might be a better permutation of the project to start with...?

This is sort of a permutation of a more ambitious version of the project wherein you'd have a similar API, but you'd be writing a scheme program that generates C code that implements the described rendering API.

The worth of the scheme one would have been being able to generate language bindings for every imaginable high level language and also be easy to embed into most existing projects.

Downside of the scheme one is that I worry I'll never finish writing it...

@aeva also if shaders were valid python, then one could simulate a frame with a cpu renderer, and be able to do things like debug with breakpoints

idly thinking about what a modern rendering api might look like for python.

you could do some cool things with the ast module to basically define shaders in python and then cross compile.

the rest of it would be a command queue thing written as a c module, and a nice data driven rendering api for setting up a compositing graph.

and some useful boilerplate like 3d model importing etc.

for the interested, emacs on android