My pet peeve with conventional commits is that some brain genius decided to shorten "feature" into "feat", a completely different word, in order to save three characters.
I suppose implementing a feature can be a feat sometimes.
My pet peeve with conventional commits is that some brain genius decided to shorten "feature" into "feat", a completely different word, in order to save three characters.
I suppose implementing a feature can be a feat sometimes.
To be frank, you appear to be set on pre-punishing a solo developer for sharing a family-and-friends project based on a rather cursory examination. Doesn’t that run somewhat contrary to the spirit of FOSS?
"The spirit of FOSS" entails the users having the four freedoms (to use, modify, share verbatim copies, and share modified copies) of the source code. You've suggested that this project is primarily binary-only with only intermittent source code dumps, meaning that until these binaries have corresponding source code they are neither FOSS in letter nor in spirit, and thus inappropriate for this community as well as for !aials@lemmy.ml, which is for AI-assisted FOSS. Given that you've suggested you will only provide source code for "major revisions" this suggests that "minor versions" never will be FOSS. Effectively you're promoting a proprietary product here that may or may not have intermittent source code snapshots.
Furthermore, the fact that you seem to consider it a great effort to "sanitize" the source code for public release suggests that what is being shared with the public is not in fact the corresponding source code to the binaries you upload.
As you pointed out the MIT license does allow you to make proprietary derivatives, so nothing you've done is "wrong" or illegal. That doesn't make it not proprietary.
Edit: I'm a different person than the admin who removed your post. I'm not suggesting your project is slop or that the effort you've put into it is inconsequential. I'm just saying that binaries without source code are not FOSS even if you publish occasional snapshots of selected releases. I'd probably be more favorable to this approach if there were FOSS builds from the source code snapshots, or maybe if only the FOSS releases were on github and the proprietary ones somewhere else - but that's probably asking a bit too much.
It's proprietary so it was always bad. The degooglers just realized it when it bit them in the ass, but before then they were promoting it all over the FOSS/degoogle community as one of the good proprietary apps.
This raises another question I've been kicking around in my head for a while - at what point does a slop project stop being slop? Say I one shot a slop app and then continue to iterate on it with human-written commits. Or I find a vibe coded app I think has potential, fork it and then iterate on it. At what point does this become non-slop, or does it ever?
You raise a good point. "Build" in software engineering has a very specific meaning: typically binary artifacts are "built" from source code. Source code I think is typically "written" but of course if you're using a generative program you can't say you wrote it...
I've seen an LLM-user claim that "AI is the compiler of natural language" so I suppose if the prompt is source code then the generated code could be considered a build artifact. But, yeah, I don't think people generally say they "build" code.
Proprietary is a deal breaker (and SaaSS is a subset of that), so if the only option is slop then I guess I have to use slop.
But, realistically, neither. I haven't found a situation so far in which the only viable option is vibe coded.
Rewriting stuff in rust was kind of a meme long before LLM's. Rust also is famously a powerful language with a steep learning curve, the latter being irrelevant if you don't actually have to bother to learn it.
My tinfoil conspiracy theory is that artcraft is actually a 5d chess move from the "anti-ai" camp to draw bigtech attention and get them to turn against LLMs on principle, or at least get them to implement some sort of anti-app-cloning thing like anthropic recently did for games.
Not really but that'd be funny i suppose.
I wonder how the rustaceans feel about their language being associated with slop.
Remember if it lives on "the cloud" (someone else's computer) then they control it... not you.
https://www.gnu.org/philosophy/who-does-that-server-really-serve.html
The biggest problem with patched apps is that they are not free software. The patches themselves might be under a free license but applying a free patch to a proprietary program doesn't cause the entire program to become free.
However, these patched youtube apps are usually promoted as competition to actual free options such as NewPipe, in free software and open source communities. So they serve as attempts to pull FOSS users back into the proprietary world. On that basis I am generally against them and promote real FOSS where possible. NewPipe and its forks (not sure about other FOSS youtube options) also have the benefit of serving as PeerTube clients, so they can be helpful in moving off the youtube platform itself.
AI is the compiler of natural language.
That's a very worrisome position. If "AI is the compiler" that means the source code is your prompts/chats and the stuff in the repo is just build artifacts.