Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RE
Posts
0
Comments
49
Joined
2 yr. ago

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

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

  • Sometimes, I just rewrite my code until it is good enough. Other times, I leave it to my memory, so I can figure it out later. And others, I'm just not happy about it, like the times I did bigbin2dec and it would only work well with something like thread-ripper.

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