which they are known to be able to regurgitate verbatim.

there are only so many ways you can write certain functions, and the most tedious part of generic application programming is configuration, where mostly there is no room for improvement; either the code is verbose or only decipherable by an established code breaker. hence modern SE has evolved certain patterns which you will find common across a variety of codebases.

Enjoy your cuck licensed software purists!

of course, where else do you think the shitposts come from? we must protect it by sending a probe to it

nothing to be nervous about, its literally software engineering and project management 101, programmer writes code reviewer catches bugs, nothing goes to production. this happens all the time, has happened in the linux kernel way before LLMs were a thing

who do you think sets the prices?

As some one here summarised it: it is to stop AI companies from getting free advertisement and endorsement, the kernel itself goes through an unbelievable amount of scrutiny so the disclosure requirement was irrelevant

its a movement, i dont endorse the projects themselves but it sends a clear message

Tell that to all the proprietary software that got OpenSourced

People against LLM parrot the same arguments again and again that it has simply lost its original meaning.

copyright status is debatable

debatable by who? who is going to settle this debate?, the courts who serve corporate greed?, Legislation made by politicians lobbied by SaaS companies? Anthropic? OpenAi? Microsoft?

The "Copyright is debatable/ its just a plagiarism machine" stance is not the Leftist/ pro FOSS gotcha argument you think it is. The point of the FOSS movement was to have total freedom over software, and that freedom includes the ability to study, learn and use it in ways it was not intended for. To stand as the antitheses of that is make Steve Balmer happy

I don't think restricting what people can post is a good idea if you are looking to grow a community

I advocate for a disclosure, blanket removal feels like censorship; even vibe coded slop is a project that might generate interest if it was made to solve some problem or showcase a new frontier, nature of OSS will push the slop out of the project eventually.

When I say "slop", I refer to a huge codebase that does what it advertise but has no documentation on what it does internally and the primary poster cannot adequately explain what it does(code mudball esentially). but if its well documented and looks like it was put together with care, with rhyme and reason than I will defend against calling it slop

Me, I’m trying to learn my way around SDL3, which seems especially interesting as it also has a GPU API so programs should, in theory, automatically use the appropriate backend (Vulkan, OpenGL, DirectX, etc) without having to write in said spec. Once I have a better idea of what’s going on and what I’m supposed to do, I might create a FOSS game engine and a bunch of video classes explaining how and why I did stuff; so, don’t expect anything concrete within the next 6 months! I love being unproductive and those hustle-life fuckers can go fuck themselves

As someone who is building said Game Engine in SDL3 using SDLGPU, I will have to warn you, the GPU api is missing a lot of features and suffers from some very annoying limitations that you have to workaround. The engine is still in development. The only reason I have not published the source yet is because I have still not figured out a satisfying multithreading architecture and also because i am showcasing parts of it as a 'mini project' for college credits. It should be finally ready soon, I have managed to get a doom style FPS working satisfactorily and the next thing I am fitting the engine for is Open World style asset streaming.

That aside, it was the first big project that I tried using LLMs for, and mostly they were used for boilerplate(SDLGPU has a lot of configuration that needs to be laid out, moreover since this is an engine, there needed to be a way to change the config from the scripting layer) and generating giant switch-case trees for input handling.

beyond that I have found that if I have written two disconnected modules that I need to connect, and if i can visualise mod1->[some sanitization]->mod2->output, I can confidently let the LLM handle that piping if i described it, but if it was even a degree more complicated than that, the LLM tended to do a poor job or radiated outwards and touched modules it shouldn't(not that it didn't give me the end result, just that it over complicated the solution or introduced 'slop')