pierogis – python/rust image and animation processing | Hacker News Reader

pierogis – python/rust image and animation processing

github.com

52 pointsksm171713 comments

What an unfortunate name, pierogi is already plural.

As someone who is fourth generation Polish in America--basically all that's left at that point is food and people butchering your last name--is that even though pirogi is plural in Polish, plenty of Americans have made pirogis the plural in English.

Try to miswrite a name of a french classic dish intentionally like you're doing here at a party or a dinner and you'll pay a heavy price in being ridiculed. I've seen this phenomenon with other things where Americans often miswrite/mispronounce names just because "it's what we call it here" and I always find it amusing.

French food is generally a different level of prestige than pirogis and gobs.

The old lady who runs our neighborhood Polish grocery store would smack me upside the head if I tried to order Pączkis!

classic misunderstanding, less like the eastern european delicacy, more like an italian geographic information system.

In Polish chips is singular and chipsy is plural, we shouldn't complain;)

unfortunate but delicious

I made a python library/framework for processing images and frames of videos. There is a command line tool to use some built-in functions, and it can be used as a library to create a pipeline of custom operations on images as numpy arrays.

Here are some examples made from the command line.

https://gfycat.com/compassionatehoarsefunnelweaverspider https://gfycat.com/neighboringweeflatfish

Some of the functions use pyo3 to bind to a faster rust backend.

Why oh why would you name your project with a grammar error.

I notice this is using the AGPL but it isn't a web application. How is using the AGPL in this situation different from just using the GPL in terms of how it affects software that uses it? Does any public facing web application that uses this library need to be released under the AGPL?

Chose it in case someone (me) makes it into a web application (in a couple weeks), and I figured it would be least likely to screw myself over. My understanding is that AGPL requires downstream to share any changes they have made to the source.

What do you mean it's not a "web application"? One surely could run this library on a server and expose it to users.

Reply on news.ycombinator.com