When I do commit, I write up the title of what I did, and describe it, and then use periods for related commits. Just easier.

For small projects, rewriting is often superb. It allows us to reorganize a mess, apply new knowledge, add neat features and doodads, etc.

This. I’m coding to contribute to a open-source software with very small amount of coders, and with a non-mainstream Domain-Specific Language. A lot of the code I did before has been proven to work from times to time, but they all could benefit from better outputs and better GUI. So, I end up reengineering the entire and that’ll take a really long time, however, I do a lot of tests to ensure it works.

I been meaning to learn Ruby to get around using Python. I like Ruby syntax better.

Chances are there’s probably something similar to dictionary in Python in your languages or at least it’s a import/#include away. Although I don’t use general programming languages at all, in my used language (G’MIC), I do something like dict$var=input where $var is a defined variable, and this way I can access input by doing ${dict$var} and that’s similar to Python dictionary. In C++, there’s hash table implementation out there via github. That being said, there are sometimes when you don’t need a hashtable dependent on the hashmap, and sometimes, it’s just as simple as basic mathematics to access data.

Seems like a good idea, I’m hoping that the syntax is sane. As far as languages goes, I think you’re missing out on G’MIC to compare as it does have things like FFT and other tools all for image processing which is just part of digital signal processing. And then, there’s Python with libraries and so on.

I only stick with these:

• pull
• add
• commit
• push

Easy.

For raster graphics image processing, I’d highly recommend G’MIC. Otherwise, Python and especially for string using regex library. I wish there was a vector graphics version of G’MIC.

I only do raster graphics image processing, so G’MIC it is. A entire coding language and it’s a library in of by itself for that.

On non-DSL, don’t have a fave. I’ll choose one of these: Python, C++, C#.

Open3D and PCL falls under independent programming language libraries, correct?

If you have any luck with it, these are what you should put in:

Here’s some list I have in mind:

Python specific Libraries:

• Pillow
• SciKit
• Numpy
• PyTorch

Independent Programming Language Libraries:

• OpenCV
• G’MIC

Domain-Specific Coding Language for image processing/computer vision

• p5.js (This is more for creative coding)
• Processing (This is more for creative coding)
• G’MIC
• ImageMagick (This is more of a converter than for computer vision/image processing)

This is why I started a thread for coding with image processing languages and libraries within community request. It did not turn out well.

Hmm, I think I will give it a star in case I need something like this. I did use regex enough to know how it works though I do have a offline regex101 software to aid into that.

And lack of forced indentations. Forced indentations gets on my nerves even if I already gotten used to it. These day, all I use Python is small code snip test, and it’s perfect for that as it strips out braces and other things which allows me to focus on a small code. I did used Python for slightly bigger things than that, but only to assist me with other coding languages, and I mainly used it for aiding into G’MIC scripting (Domain-Specific Language that is absolutely wonderful for raster graphics image processing).

Cython is a better equilavent as it does compile to C while enabling Python syntax. No one is arguing C or C++ is the best language. I’d even argue a perfect language does not exist. Simple syntax could be argued on a line to line basis, but forced indents is uncomfortable for some, and Julia could be argued to be better in that area. I’m one to hope Julia can take off.

In my opinion, it depends on your goals and scope. If memory manipulation (Probably not the correct words), and/or every bit of performance matters, or it has a large scope, then one would pick Rust/C-lang. If development time and scope is small, something like Python is better.

Source: I used C++, C#, Python, and I use G’MIC (language very much geared for raster graphics processing).