Without going into cursing or blind statements, let me show you that
you are blatantly wrong.
On 13 Apr 2010, at 17:55, Ivan N. wrote:
rmagic - is an old bastard whose time has long thrown out and
entirely adequate ruby community to forget
RMagick is being used quite a lot still, depending on the
requirements. It’s not thrown out, it’s in active development, and
although it does use quite a bit of memory, some graphic processing
just REQUIRES RMagick if you want to get something done. See bullet
number 2.
paperclip, mini_magic
Great, now tell me how you will do the following with MiniMagic:
Proportionally scale an incoming image to certain boundaries (so far
so good for MiniMagic)
Overlay the image with a transparent png to simulate the texture of
a book on it
Compose an image with the glossy scaled image from above and add a
book corner in the top left, a book corner in the top right. Then
stretch a repeating pattern across the top to make it look like a book
Generate a reflection of the resulting image on a repeating background
MiniMagic won’t get you past step one. If you think this is not a real-
life example, here’s the quick-and-dirty proof-of-concept of the
project: http://mozaiek.bronnenwijzer.be/
RMagick is used, it’s fast, it uses some memory, but nothing that our
server can’t handle and it’s stable. And to be honest, this is even
peanuts compared to some other graphic composing and processing we’ve
done with it, but I can’t show those private projects.
You could just have made your point by saying:
“If scaling an image is the only thing you need to do, it might be a
good idea to look other options for the graphic processing, like
FreeImage or mini_magic. Their memory requirements are not as high as
RMagick and they will get the job done equally well.”
Everything else you said basically tells you picked up something from
the mailing lists in the past and it grew into an pointless and
incorrect claim in your mind.