Halide, a language for image processing and computational photography
Report a link problem
Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderI saw their talk at Siggraph in 2012. This is really interesting work. The target image processing algorithms are low level. Think "How can I write the fastest 3x3 box blur for Sandy Bridge and later architectures", not "How can I speed up my face detector". Examples of scheduling decisions that Halide deals with: process image in 4x4? 8x8? 16x16 chunks? use a temporary buffer for an intermediate processing stage, causing worse cache behavior but reusing results that are needed…
https://www.youtube.com/watch?v=3uiEyEKji0M Here is a relevant video from the creator. It has some fun illustrations to help with what its going on. /edit - letters
A Domain Specific Language for image analysis that has used GPUs as well is Diderot (http://diderot-language.cs.uchicago.edu/) Diderot is very different from Halide though. I think Halide is for processing image data, while Diderot's interface is a much higher level of abstraction (program are written in terms of tensor fields, which Diderot then reconstructs from image data).
I want to see an AV1 decoder written one Halide.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 403
- Total comments
- 68
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking