After reading through the relevant threads, I'm completely on the side of the LLVM CoC committee, this user is just wasting their time. Asking for minimal steps to reproduce an issue is the bare minimum for report issues on open source projects, it is not the job of the developers to show that there is an issue, particularly when some of them attempt to do that, and are also unable to do so. The AI content in the LLVM and Mesa threads was actively misleading, confidently stating absolute nonsense, not even close to anything that was true, but still 100% confident. It's misinformation, bordering on disinformation.
(11) General Interference with Organizations and Production
(a) Organizations and Conferences
(1) Insist on doing everything through “channels.” Never permit
short-cuts to be taken in order to expedite decisions.
(2) Make “speeches.” Talk as frequently as possible and at great
length. Illustrate your “points” by long anecdotes and accounts
of personal experiences. Never hesitate to make a few appropriate
“patriotic” comments.
(3) When possible, refer all matters to committees, for “further
study and consideration.” Attempt to make the committees as
large as possible—never less than five.
(4) Bring up irrelevant issues as frequently as possible.
(5) Haggle over precise wordings of communications, minutes, resolutions.
(6) Refer back to matters decided upon at the last meeting and attempt
to re-open the question of the advisability of that decision.
(7) Advocate “caution.” Be “reasonable” and urge your fellow-conferees
to be “reasonable” and avoid haste which might result in
embarrassments or difficulties later on.
(8) Be worried about the propriety of any decision—raise the
question of whether such action as is contemplated lies within
the jurisdiction of the group or whether it might conflict with
the policy of some higher echelon.
The Mesa project example(https://gitlab.freedesktop.org/mesa/mesa/-/issues/13022) is even more deranged - I came to this story from someone on Mastodon recommending people proactively ban this person from their project. I'm not personally in favour of doing that, but this is the closest I've been to thinking that's a reasonable thing to do to prevent actively wasting time on nonsense busywork.
This would have me astroturfing it out the window after seeing this nonsense.
The output in their Mesa project bug report is outright misinformation, it sounds completely plausible but is absolute nonsense. This is the true danger of AI, it is so convincingly confident that people forget to question it, or in this case, don't even have the tools to begin questioning it. It's actively unhelpful at best.
Thats absolutely not what they asked for, no one was able to reproduce the issue, so they asked for clearer instructions on how to reproduce the issue and were met with hostility. It's not the job of OSS developers to debug someone else's scripts just to then start debugging the actual issue. This is the absolute bare minimum of any bug report, if you think there's a bug but no one else can observe it, in the first instance you have to assume it's something to do with their setup, until shown otherwise. The addition of not just wrong, but completely misleading AI summaries just makes the job of an OSS dev harder, they now have to start debugging the bug report itself to try to figure out whats parts are even facts at all (hint, most of the AI generated content was completely wrong, but sounded plausible).
Personally, the developers of both the LLVM and Mesa projects were far kinder and patient than I would have been, most OSS developers aren't just not paid to work on these projects, but are usually paid to work on other things. Taking up their time with this nonsense is very insulting to them, and the attitude that they owe the author anything at all is, as stated in the LLVM ticket, exactly what pushes many developers out of OSS development.
Notably, Apple joined the seL4 foundation, as they use it in several of their products: https://sel4.systems/Foundation/Membership/ (Not sure if they've stated publicly which, but it's been pretty well known for a while now).
The video side of things is super interesting - 4k60 ProRes is an absolutely insane amount of data (something like 12GB/s IIRC?), and the addition of ACES really makes it usable for professional work where a larger mirrorless from Sony/Panasonic/Nikon/Canon wouldn't be practical.
I also found it very interesting that their pics of this feature were with Davinci Resolve on the screen and not Final cut Pro - I guess when it comes to colour, there's no better tool.
This isn't really new for Apple, they've been doing as much AI stuff on device as possible, there isn't really any change with the A16 as far as I'm aware, just more bigger.
Siri is nowhere near Apple quality standards as it is. had a fun experience with Siri the other day where I ended up sending someone the message "I'm just leaving now what the fuck are you doing", because it heard me, and showed absolutely no acknowledgement. Not the sort of message I ever want to send to an ex, but here we are.
