Snowy

Languages and libraries

image processing library

SHOW HN2018

124points
26comments
#342of 2,155 in 2018
Top 16%of 2018 by points

How HN took it

CuriousMostly questions and neutral comments

3 positive, 12 neutral or asking, 0 mixed, 0 critical, out of 15 comments about the project. Thread score +0.23.

Design: 1 for, 0 againstDocs: 1 for, 0 againstIdea: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Design of building on numpy arrays rather than new types

    From 2 comments
    • Massive opinionated opinion ahead: I like libraries that don't invent new types but just build around established ones. I think it's great that it uses numpy arrays and doesn't…
      noobermin on HN
    • Understood. Maybe it helps that Snowy does not define an Image object, instead it simply operates on numpy arrays. See also https://github.prideout.net/snowy/index.html#interop
      prideout on HN
  • Interoperability with other image libraries

    From 1 comment
    • Something I would miss as a user is interoperability. There should be ways to read from/export to numpy arrays, pytables, PIL, OpenCV, ImageMagick, basically all the mentioned…
      ktpsns on HN
  • User-friendly API for quick image manipulation

    From 1 comment
    • Well done! Some commenters have compared this to ImageMagick. I would equate this to comparing love2d [1] to SDL. If you want a user-friendly API for quick image manipulation,…
      supernintendo on HN

Objections

  • No method chaining (daisy-chaining) support

    From 1 comment
    • Yes, I'm happy with this design decision. The only bummer is that it doesn't allow daisy-chaining, as in: ``` img = img.resize(...).blur(....).hflip() ```
      prideout on HN

Requests

  • Support for method chaining

    From 2 comments
    • Yes, I'm happy with this design decision. The only bummer is that it doesn't allow daisy-chaining, as in: ``` img = img.resize(...).blur(....).hflip() ```
      prideout on HN
    • What is the alternative besides chaining, devise a new variable name for every operation? I understand that daisy chaining can be error prone, but the alternative is so difficult…
      prestonh on HN

Questions

  • How does performance compare to PIL and OpenCV

    From 1 comment
    • Neat. How does it benchmark against PIL and OpenCV for common image processing tasks?
      staticautomatic on HN
  • Difference from ImageMagick

    From 1 comment
    • What's the overlap with ImageMagick and its pals? This meant to replace or just be a smaller-tool-for-the-job?
      jhare on HN

Alternatives named

  • PIL

    From 1 comment
    • Neat. How does it benchmark against PIL and OpenCV for common image processing tasks?
      staticautomatic on HN
  • ImageMagick

    From 1 comment
    • What's the overlap with ImageMagick and its pals? This meant to replace or just be a smaller-tool-for-the-job?
      jhare on HN
  • OpenCV

    From 1 comment
    • Neat. How does it benchmark against PIL and OpenCV for common image processing tasks?
      staticautomatic on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/17918825)