Well, as a user of DSL (G’MIC), I’m happy without packages.

I always write toy software. I derive joy from writing in G’MIC.

I used it only as last resort. I verify it before using it. I only had used it for like .11% of my project. I would not recommend AI.

I’ll admit I did used AI for code before, but here’s the thing. I already coded for years, and I usually try everything before last resort things. And I find that approach works well. I rarely needed to go to the AI route. I used it like for .11% of my coding work, and I verified it through stress testing.

I never had a issue with loops. If I feel something is off, I terminate, check code, and fix it.

I just write in a language few people really knows well. Not like I expect AI to do a great job of basing off my code.

I only used LLM-generated code once. I tested and made modifications to see if it was I want. It worked out.

In G’MIC, there’s repeat(num_of_iters,_var_name,code();); on JIT code, and repeat code_block done outside of JIT. It has while, for, dowhile on JIT too. Other than repeat, there is only do while, and for which is while outside of JIT.

Note: _var_name, can be omitted. So, if you need to just repeat a code N times, that can be removed.

Nah. I only used AI as a last resort, and in my case, it has worked out. I cannot see myself using AI for codes again.

It means that I made changes to code, so that it can work with any multi-threading strategy. G’MIC is a interpretative language with JIT support, and you don’t have any control over automated multi-threading strategy. It can be thread 0 to thread N linearly, or even interleaved. So, the workaround is to make a image of size equal to cpus count, and do the multithreading there.

Yeah, I love image processing, I worked on it for 8+ years now.

As always, I do image processing. I’m a G’MIC filter developer. Recently, did some code changes to my combinatorics tools to be insensitive to multi-threaded strategy.

People should use less Ai, and learn more how to program

Yes. Once you know how, you can see pitfalls with AI.

Interesting, but I never needed AI for coding. Well, twice, and I had to do changes, but would not use AI to generate code.

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.