4 ms·
why yet another image library? what is the difference between existing solutions? random google search results: http://image.intervention.io/ http://image.inte
by gondo 10y ago
why yet another image library? what is the difference between existing solutions?
random google search results:
http://image.intervention.io/ http://image.intervention.io/
http://imanee.io/ http://imanee.io/
https://imagine.readthedocs.io/en/latest/ https://imagine.readthedocs.io/en/latest/
https://packagist.org/search/?tags=image%20manipulation https://packagist.org/search/?tags=image%20manipulation
...
- kgabis 10y agoMaybe he didn't like other libraries? There are many reasons why you would want to write a new library. Fun is one of them.
- bhouston 10y agoI completely agree. If no one reproduced existing libraries, how is one supposed to learn library design and all the algorithms? I would love to hire people who wrote their own 3D libraries in JavaScript -- we wouldn't use their libraries of course but it would show that they have a really deep understanding and can contribute to similar software libraries.
- gondo 10y agoIt is important to have fun and to learn new things. But it is presented here as a final product, not as a learning experience. Without any explanation, it is "yet another image library" adding to the noise for anyone who is seriously looking for using some image library.
- kgabis 10y agoWhy do you consider it a "learning experience" and what makes a software library a final product? Every software project has to start somewhere and be published at some point.
- vatotemking 10y agoIt has smart crop based on entropy, ability to compare images, and bezier curves for GD which none of the existing libs have. Other libs are "image manipulation" this one aims to be an "image processing" lib. Also we need libs instead of new programming languages.
- amelius 10y agoToo many features in one library, for my taste. It would have been better to keep the smart cropping and comparing in separate libraries so other environments (nodejs etc) can benefit from them as well.
- allendoerfer 10y agoI have gone through the code before he commented here to see how he did the smart cropping (1. create histogram, 2. calculate entropy) and think he could have maybe made the histogram and the entropy calculation available as separate libraries or use an existing one, but they are not too big either and I think the use cases would anyway involve some sort of image processing most of the time. The interface to crop smartly definitely belongs in an image library, especially when it is a wrapper around a native program focused on easy of use and a clean interface.
- vatotemking 10y agoWell the field of "image processing" is big[0]. As oppose to what we are used to in php world which is just "image manipulation" (resize, crop, save to different image formats) in the context of web apps. > so other environments (nodejs etc) The algos are in github you can convert it to JS if you want. Theyre both C based so syntax is not that different. If you are looking for node.js version there is already smartcrop.js. [0] - https://en.wikipedia.org/wiki/Digital_image_processing https://en.wikipedia.org/wiki/Digital_image_processing
- deleted 10y ago[deleted]
- usaphp 10y agoWhy yet another commenter who does not bring anything new to the discussion unlike the OP's image library?
- gondo 10y agoAnd what exactly are you bringing to the discussion?