I took a quick look at the python flask code and I’m still not sure if there’s a reason of not just using Next’s server side aspects. JS can do every operation I skimmed by
Yes and no. So I did it because I honestly get annoyed with pixel operations in node js. The same thing in Python with the pillow library achieves the same things in quarter the lines of code as you would need in something like sharp in nodes
The other reason I used a Python backend was that I want to extend it to more involved image processing, like producing control net inputs or post processing the end result.
Does that make sense ? Open to better ideas though
Comments
I took a quick look at the python flask code and I’m still not sure if there’s a reason of not just using Next’s server side aspects. JS can do every operation I skimmed by
Thoughts?
Yes and no. So I did it because I honestly get annoyed with pixel operations in node js. The same thing in Python with the pillow library achieves the same things in quarter the lines of code as you would need in something like sharp in nodes
The other reason I used a Python backend was that I want to extend it to more involved image processing, like producing control net inputs or post processing the end result.
Does that make sense ? Open to better ideas though
yeah it makes sense, but if you’re already offloading everything to replicate.ai it makes less sense
just extra stacks to keep track of and keep up with
yea true. some trade offs. i'm going to look into consolidating everything into just the nextjs piece.