3 ms·
How does this compare to something like Dragonfly (https://github.com/markevans/dragonfly/ https://github.com/markevans/dragonfly/)? 1000memories's issue was wi
by anonova 14y ago
How does this compare to something like Dragonfly (https://github.com/markevans/dragonfly/ https://github.com/markevans/dragonfly/)? 1000memories's issue was with the time it took to generate 12 different versions, not the speed of Imagemagick itself. So I'm not quite sure why they needed to write their own extension. Even Carrierwave (plus caching of course) can be setup this way (https://gist.github.com/1541912 https://gist.github.com/1541912).
- johne20 14y agoI would be interested in a response to this as well....
- michaelfairley 14y agoDragonfly is quite nice, but we opted not to use it for a handful of reasons: ImageMagick itself is a actually a good bit slower for basic resizing/cropping/rotating than the library we're using in Photon; Photon is ~100 SLOC, Dragonfly is ~3500; Photos are the core of our business, so a generic solution is not likely to work 100% how we need it to (we have various legacy concerns that probably would've require more code to monkey patch Dragonfly than to just write it into Photon); Java is much better than Ruby for CPU and RAM bound tasks that need to execute in parallel. All that said, Dragonfly is a great choice for most people.