Kleptine
Up until recently with Mesh Shaders, there's really just been no good way to send this data to the GPU and read back the barycentric coordinates you need in the fragment shader for each pixel.
The article offers several options, to support older GPUs, like Geometry Shaders and Tesselation shaders. This is good, but these are really at best Terrible Hacks(tm). Proof of the ability to contort old extensions is not proof of reasonable performance!
Notably, geometry shaders are notorious for bad performance, so the fact that they list them as a viable strategy for older devices makes it pretty clear they aren't thinking much about performance, just possible compatibility.
Still, I think this is very cool, and now that GPUs are becoming much more of a generic computing device with the ability to execute arbitrary code on random buffers, I think we are nearly at the point of being able to break from the triangle and fix this! We hit this triangulation issue several times on the last project, and it's a real pain.
So in those cases, filmmakers had to counteract the limitations of the b/w transformations in the actual sets.
But which axis you care about is very context specific.
Lattice now compiles to .NET IL
A Gameplay Programming Puzzle for ECS
Writing a Fast C# Code-Search Tool in Rust
The support is great too.
A userstyle to make GitHub diffs more compact
RGB to XYZ: The Science and History of Color
The Unity Timestep (Gamedev)
Hacking Unity to Run Hidden Methods
1. I was not aware this was public. 2. I was told that all rankings should be taken in context compared to others in the 2015 graduating class. Clearly none of these people are any contender to be best in the world at anything.
The people I know on the list are certainly some of the smartest people I know, but take this with a grain of salt.
Figured I would throw it out here instead of it sitting around on my hard drive! Comments and feedback welcome!
Show HN: Simple group contact sharing
The charity idea was brilliant though.