My small Python (~100 lines of codes) codes aren’t maintainable, but I’m happy with them. I don’t ever plan to work on serious projects with Python, so I can’t say much about it’s maintainability. But, from limited experience, I’d rather use C++, C#, or in my special case, G’MIC if maintainability matters to me.

In my experience, it is.

I had converted a Python code into G’MIC, and then some one else did a Python version of my own code. G’MIC is interpretative with JIT math parser. The results:

Reversing digits in a 1024x1024 RGB image.

Python: Without lookup table and numpy - 3+ minutes

Python: With lookup table and numpy - 6.5 s (Some one else machine, but it shouldn’t take that long)

G’MIC: Without lookup table - .3 s

G’MIC: With lookup table - .005 s

And I did Lavander Binary Map on my machine, you can find code for Python version in github/gmic-community/include/reptorian.gmic:

Python: 3 s (Without lookup table)

G’MIC:.15 s (Without lookup table)

G’MIC: .05 s (With lookup table)

Honestly, I find Python pretty bad for image processing in general.

I kind of like it. I can understand where it start and end.

This is what I prefer too! I also some times prefer to use bitshift when it comes to division or multiplication of power of 2.

Also, highlighted the way you expect when you click next to braces works too.

I know there’s a lot of downvotes because there are people reading this as hate toward Python. On one hand, one can make the case that it is overused and this doesn’t bold well for those that simply can never like it’s syntax. On the other hand, Python is perfect for small scripts that isn’t tailored for a Domain or just quick codes.

I’m using G’MIC for raster-graphic image-processing, but I can do other things in it too with ease. I feel this post so much.