spinel

[Nakilon]

https://github.com/matz/spinel

Can ruby-vips compile on it? Besides distribution would there be other profits? Performance? Code generation?

[jcupitt]

Oh, that's interesting!

Though I think ruby-vips would need a lot of work:

https://github.com/matz/spinel#limitations

ruby-vips uses method_missing to route Image#add (for example) to the libvips add operation.

Maybe the crystal binding would be closer to what spinel needs? I think it uses static binding rather than method_missing (though it's been a long time since I looked at the code).

https://github.com/naqvis/crystal-vips

[Nakilon]

I'm not a fan of method_missing ..D

[jcupitt]

It's nice, in that it makes the binding mostly self-updating. ruby-vips discovers the libvips API at runtime and presents it to the user.

Without it, ruby-vips would need to be regenerated every time we did a release. The drop in maintenance effort is really nice (for maintainers).

[Nakilon]

Do you mean these "docs" are just for the reference but the actual available set of methods can be different?
https://github.com/libvips/ruby-vips/blob/master/lib/vips/methods.rb
What is the "regeneration" procedure? Can't it be done on require?