Concurrent Ruby VS ruby-vips

After this, I took a look at the semaphore class in the popular library, concurrent-ruby to see how they implement it, and I learnt about something new: condition variables. And Ruby comes with this included!

As I could not find a clear example about how to rescue exceptions from Concurrent::Promises (part of the Concurrent Ruby gem ) I read through the documentation and here are two examples: one that documents success case and one that shows what is happening when there is an error.

In a sense the GIL (or actually GVL as it's called in current ruby versions) has already been removed for ruby.

It's only the original MRI Ruby that still has it several over Ruby implementations already removed it. e.g. JRuby.

Concurrent-Ruby[1] is probably a good place to start if you want to work with GVL free ruby on JRuby. It's quite well supported and is currently used by Rails.

If you just want async or non-blocking IO I'd take a look at the Async Gem[2]. It looks pretty solid in Ruby > 3.0 and it's been invited by Matz to be part of the stdlib, which I think is a pretty good endorsement.

For MRI itself I don't think it's likely they'll ever remove the GVL. Ractors are probably a better solution for CPU concurrency in the long run, although I think they're pretty experimental currently.

1. https://github.com/ruby-concurrency/concurrent-ruby

I’d highly recommend the concurrent-ruby gem that has implementations of various metaphors of concurrency, from async to promises, as well as edge features such as actors.

yes, but `Future` is being deprecated according to the docs. This syntax should possible with Promises (although on my library, it is not working as I expected, I need to look into it hahaha)

Concurrent Ruby

https://github.com/ruby-concurrency/concurrent-ruby seems to be the current king of concurrency in Ruby. A lot of different concurrency models are implemented so you can pick whichever makes the most sense for you. The downside is that since the library doesn't focus on one model over another, it's probably difficult to learn for beginners.

i think not: https://github.com/ruby-concurrency/concurrent-ruby/issues/899

Photein uses Minimagick for image management and conversion. Have you had a look at ruby-vips? From what I hear it should be better/faster/use less memory than ImageMagick, especially for the standard image formats.

A special mention to ruby-vips, which is (along with maybe php, I guess) one of the few language bindings maintained by the author of libvips, which should become the defacto image processing manipulation library.