I've writing a Rust based canvas engine, with content via my own IDE, the runtime is fed data via WebSocket using my own API protocol, web proxy routing through a streaming and distributed load balancer using a new protocol, landing on my back-end platform running my own language, writing deltas to my own data store. https://www.adama-platform.com/
It's not quite yak shaving, but it certainly is... something:
> I mean, we are running Access in Wine in X11 on Linux in an isolated
user account on our server slice that revision controls your Access
database in git, and we're displaying it using VNC in your web browser
in flash. People can't possibly want that. But they need it.
That’s the total opposite of yak shaving, but in the most hilarious way. Layers upon layers of systems and protocols to maintain legacy systems… lazily use a bunch of glue and duck tape to build the whole thing… and it miraculously works!
I always wonder why the Access database isn't moved then from JET to some database server, even MSSQL (Postgres would also work), and then you can continue Access but without needing to snapshot it in weird and possibly broken ways?
I've writing a Rust based canvas engine, with content via my own IDE, the runtime is fed data via WebSocket using my own API protocol, web proxy routing through a streaming and distributed load balancer using a new protocol, landing on my back-end platform running my own language, writing deltas to my own data store. https://www.adama-platform.com/
Why? For board game glory!