It's time to clean up GoRender and establish a solid base for adding all the lighting, shading and multiple output targets a full-featured sprite renderer needs. One thing I've noticed is my "iterate and stabilise" mode has rather less "stabilise" than I

Last time round I had got to the point of raycasting a silhouette on a spritesheet, with a largely clean solution that only had a few areas of potential messiness. I think the last useful thing I can do in terms of "learning Go while cleaning up an old

The next step for GoRender is an easy choice. I want to write the raycaster, a critical part of turning voxel objects into pixel sprites. The C# version involves a lot of vector mathematics, so implementing it in Go will touch on yet another new area. At the end of

I'm back on the Go trail, and I have two options for what to do next: 1. Improve my existing code with better knowledge of the IO libraries. 2. Port across some more Transrender functionality.

How do you learn a new language? Books, practice and a decent chunk of pair programming with someone who knows what they're doing, if available. Those are my favoured options, and when it comes to practice there's nothing like converting an existing piece of code from