eidolon @shaderphantom@awoo.space

very stable language Rust where none of my shit compiles anymore the current stable builds

1.13 is literally smaller than launch WoW

how is the 1.13 client 2 gigs smaller than 1.12 wtf

ohgh, WoW Classic is tempting

alpha is a good boy

hi. i bought an EWI 4000s today. it's going to take 2 weeks or so to ship from japan. what kinds of things can i do to practice before i actually have it in my hands

🦀 🦀 DAVID KOCH IS DEAD 🦀 🦀

Oh my God today is fucking BLESSED

"why?"

I wanna use Kotlin coroutines to handle vkWaitOnFences and other blocking calls as an experiment

I committed a crime by writing Vulkan code on the JVM

this evening is either a "indulge heavily in graphics programming" evening or a "get cozy under a blanket and watch babylon 5" evening and i'm not sure which yet

activitypub needs a new activity type for when i go to the bathroom on the public timeline

folks, maybe it's a bad idea, ...

feelin' bored, might post controversial takes

Vulkan is good

oh yeah. no upcasting. that's why.

maybe it's because trait objects are constructed very differently from C++ vtables that we tend to shy away from them. but maybe trait objects really could help us solve a broad class of issues without diverting to more academic data-oriented design solutions and without losing out on that much performance

this leaves me to question the Rust ecosystem's approach of making everything generic by default; monomorphization is expensive though the runtime is very very fast, but maybe the value in monomorphization isn't universal and we should be using trait objects more than we do?

huh. AActors also are just associated with root USceneComponents in the world, which is why actors aren't treated like a scene graph.

which leaves the question, how does the engine handle multithreaded anything with the way it's architected? for as modern as this engine is, it seems very traditional in its architecture...