Servers are on AWS and Cloudfront. We started out with three.js for rendering but we froze at 78 and are currently working on rewriting the renderer to not use the scene-graph and instead move to a more data oriented design.
Yep! It's very interesting, but our problem space is a bit different because we can do some optimizations based on our models being voxels. Great stuff though!
Why did you use GO for server side ? did you test with other teach ?
Can you share how your server side design of servers looks like ?
Do you use simple ec2 or what ?
We went for Go as it's 1) about 100x faster than Python in testing 2) Garbage collected so prevents many memory-related bugs (many of us have a C++ background so we're familiar with manual memory management and its pitfalls) and 3) It's super stable.
We did look at Rust, but Rust suffers from a little bit of the "shiny new thing" syndrome. We have simple needs and wanted something fast and boring :)
The server-side design is also as boring as possible, just standard web stack for serving, and websockets for multiplayer. We use EC2 for everything yep!
The original IGT binary version on EEPROM? Probably 2Mb, but also including all gaming machine monitoring code, attendant screens, device drivers, network protocols etc, with room to spare on the EEPROM.
