> That's because this post is about HDR

It's about HDR from the perspective of still photography, in your app, on iOS, in the context of hand-held mobile devices. The post's title ("What Is HDR, Anyway?"), content level and focus would be appropriate in the context of your company's social media feeds for users of your app - which is probably the audience and context it was written for. However in the much broader context of HN, a highly technical community whose interests in imaging are diverse, the article's content level and narrow focus aren't consistent with the headline title. It seems written at a level appropriate for novice users.

If this post was titled "How does Halide handle HDR, anyway?" or even "How should iOS photo apps handle HDR, anyway?" I'd have no objection about the title's promise not matching the content for the HN audience. When I saw the post's headline I thought "Cool! We really need a good technical deep dive into the mess that is HDR - including tech, specs, standards, formats, content acquisition, distribution and display across content types including stills, video clips and cinematic story-telling and diverse viewing contexts from phones to TVs to cinemas to VR." When I started reading and the article only used photos to illustrate concepts best conveyed with color gradient graphs PLUS photos, I started to feel duped by the title.

(Note: I don't use iOS or your app but the photo comparison of the elderly man near the end of the article confused me. From my perspective (video, cinematography and color grading), the "before" photo looks like a raw capture with flat LUT (or no LUT) applied. Yet the text seemed to imply Halide's feature was 'fixing' some problem with the image. Perhaps I'm misunderstanding since I don't know the tool(s) or workflow but I don't see anything wrong with the original image. It's what you want in a flat capture for later grading.)