You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like some stability issues cannot be completely nailed, stack too big and not everything is in scope. The current end to end stack covers
python, go (interfaced with gopy) and C for some lower level libraries (like libvips)
Salient issues are that
speed is lower from the python side post golang 1.18, hard to address without diving deep in gopy
govips doesn´t expose the whole libvips interface, and while all vips calls can error out and these are caught, vips can hard crash on some images when trying long enough
It is possible to remove the libvips dependency and stick to pure Go on the image processing side, but we become CPU bound in this case.
Moving to Rust -and sticking to Rust native code- could remove one layer in this stack (no more C give or take), and benefit from more compile time guarantees
The text was updated successfully, but these errors were encountered:
Looks like some stability issues cannot be completely nailed, stack too big and not everything is in scope. The current end to end stack covers
python, go (interfaced with gopy) and C for some lower level libraries (like libvips)
Salient issues are that
It is possible to remove the libvips dependency and stick to pure Go on the image processing side, but we become CPU bound in this case.
Moving to Rust -and sticking to Rust native code- could remove one layer in this stack (no more C give or take), and benefit from more compile time guarantees
The text was updated successfully, but these errors were encountered: