Why would somebody ever want to take perfectly fine code history and erase it? Phrased like that it makes git squashing seem ridiculous. Alas, some
As types are a keystone in Leaf, working with them must be fluid and simple. I recently improved this area by adding named constructors and
I needed pleasant range values for the charting API in Fuse. These are the values written by the ticks on the plot, typically on the
Language support for caching sucks. Despite an ever present need to cache data and calculations most languages require the programmer to do all the work.
The flexibility and usefulness of an API relate directly to its orthogonality. But what does “orthogonal” mean? It’s a term that’s tossed around a lot
I can’t decide whether a.size or size(a) is more correct when getting the length of an array. While writing Leaf I have a recurrent feeling
We used a lot of object normal maps in RadialBlitz. Figuring out how Blender encoded these was part of the challenge. It didn’t seem to
A simple tap of the screen invokes a staggering amount of calculations. That screen is actually big tree of UI elements, and we need to
I came upon a problem with bitwise complement (logical not): it isn’t safe. It’s nothing new, but it really registered while implementing the logical operations
Now that we’ve drawn beziers and arcs there’s only one piece missing in the vector API. We need to calculate the bounds of the curve:
Signup to my mailing list to get notified of each article I publish.
Made with Elementor. Hosted with SiteGround. Domain from Netim.