Based. This is great news.
Linux
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
I would say yes and no. I don't think it's entirely horrible as a programming assistant. I used it just a week ago to perform a series of UI upgrades. I probably wouldn't have learned anything doing it myself, just mindlessly following the upgrade guide until it's all done. It would've taken me a day at least, between meetings and other distractions, but an agent did it for me, unattended, in about 5 min. I still verified functionality afterwards and fixed a couple tests.
In some respects it kind of feels like the argument I had with a coworker over the use of Lombok (a tool for injecting common but often tedious coding patterns in Java). I was on the side of not using it because some of the patterns are important to understand and not understanding the implementation can lead to misuse of them. Eventually I decided it was a "necessary evil" and that using stuff like that could free me up for tackling the stuff that is completely unique and wouldn't be found in any library. The fun stuff.
I still hate data centers and AI revenge porn and AI scams and people that replace perfectly functioning tools and experienced workers with AI bots that aren't nearly as reliable. But I don't think it's an inherently bad technology.
I recently got assigned to a project where portions of the UI has been LLM vomited. It does not conform to web standards, and it doesn’t give a fuck about accessibility.
There’s a custom checkbox component whose label isn’t clickable. I’ve had to fix so many little things because someone couldn’t be bothered to do it right and chose to outsource their thinking to something that can’t think.
My view on LLM usage is essentially, if you don’t give a fuck about what you’re doing, why should anyone else? If you don’t care enough about your project to actually develop it yourself, why should Flathub platform it?
So this is some what problematic. Technology has benefits does not mean it has to be allowed. Question is what do we gain and at what cost. If the answer is we gain speed, then the followup is "does it really matter?".
Speed of coding is the common answer. Another one is non programmers are able to make programmes. Both of it does not add much of a real value is the point. Because when the machine churn out code at a very high rate, then the humans who should review it gets under pressure. We are not addressing the real bottleneck, instead we just pump out more material which just intensify the congestion at the bottleneck. Quality goes down, we get things like AWS going down, Microsoft wiping people's machines, etc. In other words it creates problem without much meaningful gain.
Regarding the non-programmers making programmes, it mostly just create a lot of noise. There is a lot of weekend projects, one shot attempts, or some half cooked outcomes. Only a handful of projects with meaningful impact in the world will be born out of it. We all know, even before AI, out of hundreds of thousands of GitHub repos only a small section is actually well maintained, and deliver something to the world.
I don't have to explain at what cost. It is just literally affecting the climate and accelarting the collapse of current ecosystem. Are we doing this so that a code can be written in 1 hour, instead of one day? If you get more free time because of this, well, at least we can say the load is reduced. But we all know we just get more work to do from our employer. So I don't really think this is a net positive.
We all know out of hundreds or thousands of GitHub repos only a small section is actually well maintained, and deliver something to the world.
...That was literally no different before AI.
Oh. I meant before AI only. I should have clarified that.
How can they tell if it's AI-assisted?
if you are remotely a dev, you know first sight
What if I’m in-office dev?
Then you can't tell. Sorry, I don't make the rules.
That is an absolutely terrible standard. In fact, that's technically not even a standard. The "I know it when I see it" measure is literally the logic used in censorship. It allows cognitive biases to seep in with no check. A lack of hard metrics means that there' zero ways there can be any objective consistency. And finally, this kind of rationale makes the biggest sin that I can think of, "non-falsifiability".
Whatever people's opinion on AI are or are not. This logic should wholly be rejected in every instance it is brought forth. It is literally the antithesis of rational thought.
no, as someone whose entire job is code reviewing ai slop you LITERALLY know at first sight just by looking at it what is written by an LLM and what is written by a real person.
as someone who has a similar job, i don’t think it’s so obvious. there’s a lot of middle ground between an AI slop PR and artisanal, hand-crafted code. if i use a library or algorithm or pattern suggested by ChatGPT or use Copilot to autocomplete a simple function or have Claude generate test cases, that’s all “AI assisted”.
Sure, but that's not what this is about. This isn't just banning AI-written code, it's banning AI-assisted code. If you even use a Google Gemini "AI-summary" at the top of your search results for something simple like the name of a function, then your code is AI-assisted.
There's no way anyone can detect that. And banning it is silly.
But the point is, imho, that if nobody can tell if it's AI-assisted, then who cares? This is more for them to fire a warning shot that you'd better be sure your AI-assisted code is good enough to pass, or they can reject or and, potentially, ban you without notice.
I agree that you can tell if the whole code base is AI written. But stuff like dependency upgrades being handled by an AI is impossible to detect, IMHO.
That reminds me of my friend who said (a long time ago) that Japanese girls are prettier than Chinese girls, I asked him how he recognises them, since I knew he didn't know any Chinese or Japanese personally, he said, that when he sees an Asian girl, he just knows, if he likes her, she is Japanese , if he doesn't like her she must be Chinese (and no, he didn't talk to any of them to confirm his "genius" theory... Hey, we were both young, talking to girls was difficult, even more difficult than realising there are a lot more Asian countries than just two)
What I meant is: it's stupid, if you recognise AI assisted code because it's bad, maybe just say that you don't accept shitty code
I'm no competent, or no professional, dev, yes, but I absolutely cannot tell if it's AI generated, let alone AI assisted(whatever that is) code.
That only was the case with ChatGPT3.x era.
Well, I was already sold on flatpaks, but now Flathub is going to be my main repo.
And yet another reason to use it instead of snap.
Good. I hope this puts a dent in the number of new projects that use AI. I also hope Flathub implements a system to clearly flag existing submissions that have used it.
There is no way people will change their workflow because of flathub. They will just not use it anymore.
I wasn't a fan of flathub or flatpacks but this gives a glimmer of hope that there's at least a glimmer of hope for it.
But my app I'll have no idea how to maintain?!
It's silly. They even acknowledge that AI-generated code is inevitable and that exceptions will be made. Looks like a (hopefully) temporary measure to give maintainers some space to breath.
Death and taxes are inevitable as well but I don't see yall being earlier adopters for that
Pointless exaggerations aren't inevitable either, but you adopted and shared one. Pointless and "witty" exaggerations won't change the outcome of the process though. Which is why robust and transparent AI policies are required.