I was unsure whether to exhumate some old threads on the same topic, so to avoid necroposting, here is a video with a collection of my projects, most of which were created by converting some of my previous projects from yab to C++ with the help of different llms.
It’s a video so that those who are not interested in the topic can simply choose not to play it.
Cool! Download links? Or are you planning to get them into HaikuDepot?
Thanks, probably if someone is tempted to test them I would share the packages…about publishing them, I’d like to release them as MIT, but code generated code is still controversial, I think; I instructed LLMs with my yab code or feeding them sources from other MIT licensed applications (for example, the minimizer replicant has been instructed from DockBert, SpielBar uses a lot of code from tracker, in both cases this is code I selected and gave to the LLM, so I’m sure it’s MIT), so probably there is not code from gpl or closed license sources, but in doubt, I prefer to not share anything atm
Great tools to have and use!
Good to see some, yab to C++, Haiku/BeOs apps alive!
TeXTile is working with Falkon? Drag’n drop the @ for example?
CatchAll looks very helpful too…
In doubt, some dev cold have a look on the source code?
Adjust it if necessary?
this is the original intent, due to the limitation of keymap support in wayland apps
Great stuff! Can you please post the source somewhere so the dev’s can see if we can put it in the Depot.
Is that a model you trained yourself? If not then it was likely trained on other peoples code
No, so this is one the reasons to keep them into a private repo, as I wrote above
FWIW, HaikuPorts already carries at least one package, not only “made by AI” (and licensed with MIT somehow), but even with the copyright set to: “2024 Claude 3.5 Sonnet, Gemini 1.5 Pro”, which I particularly found very weird (unless someday computers get personhood… can copyright even be assigned to them?), but… what do I know.
Recipe in question: screensavers_ai.
There was a thread about them on this forum too.
I credited AI as the author of this package for the simple reason that the code doesn’t contain a single line of human code. This was an experiment to see if AI could write a fully functional Haiku application from scratch without human modification. As part of this experiment, I also asked AI under what license to publish this code.
thanks to @Nexus-6 to his input, this is how TexTile looks with no button borders, bigger font, and a more standard menu bar
Yeah, that sounds like a mistake and should never be shipped…
Why? I explained above the essence of this fun experiment and why I indicated authorship in this particular way.
If you trained a new AI Model on your own works only you would have copyright, but taking a model that was trained on other peoples work effectively means you are just taking their code without attribution. Code “generators” cannot have copyright, neither can other forms of text autocomplete. Haikuports should not ship anything with unclear or clearly wrong copyright.
You don’t get jokes? That’s your purely personal opinion, and if you conduct such AI experiments, you’re free to do as you please and list all 8 billion people living on planet Earth as authors. That’s your right. But I don’t care, and I’ll do as I see fit.
One question: did you learn C++ and programming from books written by other people? Why don’t you list the authors of those books as co-authors of your code? ![]()
I think that most forum followers got the joke but somehow Haikuports is too tied to Haiku. Nobody would like to see that main depot down hence an approach a bit more strict there. The same package hosted on LOTE wouldn’t be a problem.
so does it work?
The haikuports publication guidelines only restrict the submission of statically linked applications with web engines like Electron. I don’t recall any prohibition against submitting AI-generated applications. Furthermore, a huge number of modern projects and individual programmers are already using AI tools like Copilot or Claude Code in their development. Whether you like it or not, that’s the reality. And if you start filtering PR to haikuports based on this, you’ll end up with nothing.
I think they’d rather end up saving the good reputation of Haikuports from A"I" (sic, mind the quotes) pollution.
21st century Luddites )))
