What will make YOU actually use or reject the image library?

p0nce said:

"The reasons that will make me interested in the end are cold and mechanical: is it maintained? does it load image files (progressive JPEG and normal PNGs)? quickliest? usable without runtime?"
"I tend to reject libraries that aren't on DUB, that impose bizarre flags, that don't work on the 3 desktop OSes, or seem to expand important energy on trivialities or strange wrappers. Preference for a few larger files."

Manu:

 I have no motivation to write code that I can't use in my own projects. (numerous, including Dreamcast game)

- must support a @nogc path with concern for allocation (which is inline with modern phobos; a la std.experimental.allocator)
- must be relatively small binary (pay as you go)
- GUI rendering at least as efficient as ImGui
- must have swappable rendering backend (ie, backend abstraction)
- must load common useful formats

NX1337:

integrity
I don't know exactly but if it doesn't suck chances are I'm gonna use it
because pretty much anything I used I wasn't pleased with
(in D)