I personally have email integrated into my editor (mu4e) so I can apply patches and search code directly from the email thread. It handles threads and searching really well.

Your making a big assumption extrapolating from one particular study involving Java code and a static analyser.

How is that patch sloppy?

I feel the term slop is being overused to cover anything an LLM has touched. If I ask an agent to re-read a mail thread for me and apply the changes to my tree to review is that slop? Would you feel better about it if I copy and paste from email to code in my editor?

I’ve just been doing a bunch of bug triage which was mostly driven by the agent although I checked the issues where it had commented. Was that slop? Ironically a lot of the issues where AI generated although for the most part more complete than a lot of the purely human submissions we get. Are those bug reports slop? What about the poorly drafted human ones?

That’s not kernel policy but LF guidance. From the kernel’s point of view patches still have a high bar to pass to get merged and I don’t think we have enough data yet to see if LLM based submissions to the kernel have a higher or lower error rate than humans.

I certainly feel the uptick in LLM reports though - one of the projects I’m working on is seeing a deluge of them at the moment.

I’ve vibed a bunch of apps and scripts and it’s great for that project you never found time for. Importantly they where all local and ultimately throw away things.

The idea of relying on vibes for production seems insane to me. The most important thing about software engineers is not how fast they can type.

At 43 that’s probably a little earlier than the OP expected and if their daughter wasn’t planning on starting that early it’s going to affect school and job prospects.

That’s not too say it can’t work. One of my in-laws had their first at 18 and now as their last leaves for uni they are still fit and young enough to enjoy the empty nest experience.

To be honest I think windows work better as sun traps. Even in the winter a good sunny day will make a noticeable difference to my bedroom with large south facing double glazed units.

Even Debian has popcon as an opt in. I can see why collecting data about hardware and package choices is useful to Ubuntu. I didn’t think they collected any personally identifying information.

It will be fun watching those users who first make the jump to the new project.

If it’s finding valid vulnerabilities then it’s just another tool like static analysis, fuzzers and sanitizers. There definitely seems to be a difference in quality compared to earlier generations that were behind the sloppy avalanch of reports.

I think the article is over complicating things. I work in a project which is heavily forked for a variety of reasons. While it’s academically interesting to look at the reasons for those downstream forks we have no interest in going to the considerable effort of tracking them all.

If you can take a project and use an LLM to enable your niche use case then more power to you. FLOSS was never about ensuring all patches flow upstream.

I was glad to see Niko publish his initial work and look forward to seeing how it’s gone.

So algorithms then?

LLMs have some interesting properties and certainly can do a good job sifting through large amounts of raw data. They are however a very brute force approach compared to say a network routing protocol. Sooner or later people will start to realise (again) that engineering is about trade offs and you need to work out what your constraints are and stop trying to solve every problem with massive amounts of multiplication.

I swear people have rose tinted glasses as to the state of the init system before the current generation of system management daemons.

If you really want to have Debian without systemd there is always Duvean but the Debian architects are free to choose the technologies that solve the very real system orchestration problems that exist.

The amount of drama bait this caused over the last week was something to behold.

I like to think I’m reasonably technical and I do put network and some devices restrictions on their accounts. However stuff still gets through and I don’t really want to play a cat and mouse IT admin game with my kids. If I as the root user could set the field on their PC’s and that would allow them to access age appropriate services without having to hand over personal data to some age verification service then i’d consider that a useful feature.

When they get the keys to root they can set it to whatever they please.

It was worse than that. Our understanding of radiation took awhile. While Uranium glass is probably safe I wouldn’t go using it regularly. A lot of women (“radium girls”) suffered from cancers induced by licking their brushes when painting luminescing instruments. This comic looks like 50s era when post the bomb sci-fi was full of “atomics” as the stuff of the future.

Normally you try and cost reduce the BoM and split the difference. RAM seems to be out striping any cost savings you can normally make updating the hardware.

Who are the community employing? Why do they need consulting before code changes are made?

What a pointless drama article this is. FLOSS software does stuff for legal compliance more often than you’d think. The whole point is people can contribute fly by patches and the maintainers make the decision to merge. It seems like being an optional field but potentially providing useful functionality is enough for systemd. If you don’t like it I’m sure there are forks you could join or even use a different init system. No one’s freedom is being oppressed here.