RE: https://mastodon.sdf.org/@argv_minus_one/117207930196699334
yeah, so when LibreOffice repudiated the AI, that was what we call a lie
0 Boosts
0 Likes
@davidgerard@circumstances.run @atax1a@infosec.exchange
The answer to how much code the bobot should be trusted to write is zero. In Dutch, nul.
@davidgerard@circumstances.run @atax1a@infosec.exchange
Will LibreOffice be able to get back on the right path? I don't know. I hope they do. But I am afraid that it might be too late and that we'll have to cross off ANOTHER project because I guess actually having any standards at all is now verboten when you can just replace your brain with the bobot which surely will last forever after all "AI is here to stay" right what do you mean impending economic crash what do you mean hundreds to thousands of dollars per token is how much it actually costs and the subsidized model is unsustainable that's just evil FUD what do you mean no it isn't I declare AI is here to stay and therefore it is.
Yes that last sentence was deliberately mangled and incomprehensible, I don't respect these people enough to put any thought into mocking them in a way that is comprehensible.
@daemonspudguy @davidgerard @atax1a
> Will LibreOffice be able to get back on the right path?
Given that the output to the master branch is a guestimated 95% either leeched manual backports from #CollaboraOfficeOnline authored work or slop these days -- unlikely.
https://openhub.net/p/libreoffice/contributors?query=&time_span=&sort=twelve_month_commits
heh, glad that I forked GratisOffice before the slop started.
@davidgerard JFC. They used an LLM to write 24 lines of code AND STILL HAD TO DEBUG THEM.
“The copyButtonHandler method was manually created and had
support from LLM/code completion. (lines 330-353)
The patch is open to further suggestions for simplification
and code improvement or refactoring.
Some lessons learned: LLM cannot guess solutions for wide
and open demands. Narrowing the query to code fragments
produces acceptable and easily debuggable code.”
@LabSpokane @davidgerard the "using slop for debugging" demo at our day job had a guy sitting there telling us "uhhh, the model you choose sorta doesn't matter, and also you have to tell it where the bug is"
totally useful technology, love having to pay money to sam altman to do debugging by telling a chatbot where the bug is, makes lots of economic and logical sense
borat voice not
@LabSpokane it really shows that Collabora was doing the work in the project
@LabSpokane really hope they haven't gone slop
@davidgerard The comments alone should make the case, but we’re in the stupidest of all the stupid times ...
@davidgerard What does the post say?
@kimcrawley that's three openly chatbot patches
@davidgerard@circumstances.run
Their response to being called out for using the bobot (I'm blaming @atax1a@infosec.exchange for me learning of that word as they're the first person I remember using it) is exactly as bad as you'd think.
https://fosstodon.org/@libreoffice/117214068793979843