It looks like you could use thumbor (or any similar solution) as an external resource[0], so it doesn't matter what language it's written in.
That said, it usually feels safer to have something that works with the same stack.
We're using carrierwave, and it's pretty neat, but we had a few times where we had to scale thumbnails differently, and it turned out to be a pretty long batch operation, especially since we're storing images on S3.
I think that 'on-the-fly' conversion and caching could work better for larger sites that tend to change. Pre-processing doesn't scale so well.
That said, it usually feels safer to have something that works with the same stack.
We're using carrierwave, and it's pretty neat, but we had a few times where we had to scale thumbnails differently, and it turned out to be a pretty long batch operation, especially since we're storing images on S3.
I think that 'on-the-fly' conversion and caching could work better for larger sites that tend to change. Pre-processing doesn't scale so well.
[0] take a look at https://github.com/rafaelcaricio/thumbor_rails, which I believe is using https://github.com/thumbor/ruby-thumbor
EDIT: added links