Floating point rasterization brings me back to 1993 style rasterizers (when I was 5…) and all of the problems they entail. Dropouts, double renders, endless edge problems, seams… rasterization is a lot of fun. It’s one of the only areas I can think of where fixed point isn’t merely a feature, it’s a necessity.<p>Not that rasterization was the point. :)<p>Ironically, I searched for a reference explaining all of these problems, and wound up finding my own HN comment. <a href="https://news.ycombinator.com/item?id=21736821" rel="nofollow">https://news.ycombinator.com/item?id=21736821</a> (Who said HN results rarely show up on Google?)<p>That five part Chris Hecker rasterization series really is the jams though. It covers so much ground, and it even has code that can (with effort) still run. I’ve wanted to reimplement it in JS and make a web version.