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#.

Every languages has their own pitfalls. The answer on picking a language is to pick whatever works for you. There may be even domain-specific languages if you’re interested in a domain, and it can be way more flexible than general-purpose solutions for that domain too.

I use 4 languages.

1. C++ for adding features to a program.
2. C# for making .dll for an application (Paint.NET). Kinda similar purpose to what I do with G’MIC, except so much more limited.
3. Python for processing strings
4. G’MIC for creating/editing raster graphics images (volumetric too)

Now, I wish there was a vector equivalent to G’MIC, but there isn’t.

Braces too can be wrong. But, one is less likely to get it wrong. Modern editors often allows one to highlight matching braces immediately after selection, and rainbow braces(if available) makes it clear on the nest level.

I didn’t say it doesn’t help. But, it alone does not really help for bad and long code, but you are correct in that it would be worse with the wrong indentation. Like you pointed out, the program could do the wrong thing if there is a wrong indentation where indentation matters which is one of my issue with something like Python. And languages with explicit exit scope tend to not have that issue while adding to the benefit of making longer code readable. Where white-space sensitive languages really shine on in my opinion are small codes, and that’s where I think of using Python.

From some one who used Python as it was the easiest solution to few of my problems, and having to experience languages with brackets and/or endif/fi/done as ways to limit scope, I find that having things like brackets and/or scope terminators easier to parse and less error-prone. I’m thinking about moving on to Ruby whenever I had a need where Python would be a good choice, but the time it takes for me to understand a new language is blocking me from that.

Well, artists would disagree on that point, and I do agree with the artist. I do think ML at this current state and near future do have a limit. I can’t see ML doing anything complicated in 3D like a CAD automobile any time soon.

Indentations does not really help readability that much in case of really, really, long code, and in some cases, a code can execute without with unexpected result because of one single indentation being off. Both of these why I like things like curly braces/brackets and terminators like endif/fi/done/end/etc. But, at the end of the day, if there’s a readability problem, then that’s a sign that the code needs to be reworked on.

My crazy take is that there needs to be a interpretative language alternative to Python which uses brackets to define scope and/or things like elif/else/fi/endif/done. Much easier that way in my opinion, and the “;” shouldn’t be necessary. I’m used to Python, but if I had another language which can be used to serve similar purpose to Python with those features, I would never code in Python again when it comes up.

Having to code in Julia and G’MIC (Domain-Specific Interpretative language that is arguably the most flexible for raster graphics content creation and editing), they’re the closest to there, but they’re more suitable for their respective domain than generic ones.

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).