@Fedihacker IMO you underestimate on how many ways you could solve the same problem.

Besides I'm talking about:
- Porting types that were not present in source, but existed in past versions & my code.
- Porting names that didn't exist in source, but exist in my implementation.
- Using highly un-idiomatic design choices, not present in source. Tbh. I haven't found them anywhere outside my lib.

It's way too specific to be considered "anyone would write it this way".

It's sort of eye-opening experience, as person very familiar with the plagiarised source you can see how LLM is stitching together fragments of code seen somewhere else. It's just that most of the time we don't know the original code that AI reused and cannot notice the stitches, so we consider it to be an original writing.

gl;hf to all the people using AI to write code in a domain where GPL source was available.

I've asked Claude to implement a Rust port of JS library given source code in another directory: there's already one such implementation in OSS, mine. Result?

AI blatantly plagiarised my OSS code, including parts that were not present in source it was pointed to port.

Upon prohibiting it to touch outside implementations and focus on translating local directory... it ignored command and plagiarised my work again. It did the same with C# port and one existing impl.