axman6

Joined 17 years ago

Karma
497
Submissions
318
Member since
Nov 22
Hacker Newsers URL:

[ my public key: https://keybase.io/axman6; my proof: https://keybase.io/axman6/sigs/iW_swLHLPyPBft7t-R5kHZD3ZCHhIX-7pBUTbVj6yBQ ]

View on Hacker News

Recent submissions

Comment · 1 year ago
I wasn’t expecting to personally know two of the authors, but having Accelerate included makes sense.
Comment · 1 year ago
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.

It actually reminds me of the the [OSS Sabotage book](https://www.cia.gov/static/5c875f3ec660e092cf893f60b4a288df/...)'s section on General Interference with Organizations and Production (page 28):

    (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.
Comment · 1 year ago
> Do your job

"I'm a volunteer, my job is to choose where I volunteer my time, and I won't be volunteering it for free for this".

Comment · 1 year ago
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.
Comment · 1 year ago
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.

Comment · 1 year ago
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.

Comment · 1 year ago
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).
Comment · 3 years ago
Oops, yes indeed! Was working from memory and should’ve checked.
Comment · 3 years ago
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.

Comment · 3 years ago
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.
Comment · 3 years ago
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.
Comment · 3 years ago
The only thing worse than Apple fanboys is anti-Apple fanboys projecting.

No one is going to claim this. The fact the Pro gets 10Gbit USB 3 _is_ interesting (particularly for anyone using the phone for video), but certainly not revolutionary or genius.

Comment · 3 years ago
They used to sell the case, and each airpod separately (with the total for all three being the same as a new pair), but it looks like they stopped? It was very useful when I ran over my airpods case with my LandCruiser, and it got a bit wonky (but was amazingly still fully functional).
Comment · 3 years ago
That sounds highly unlikely, the one that came with my MBP supports everything up to Thunderbolt. But USB is ridiculously complicated, and sometimes better cables fail on shitty devices; I've seen it a few times with camera equipment where I really needed the cable that came with it because higher specced ones just didn't work.
Comment · 3 years ago
Paul, are you actually for real right now? Did you really just say "We deleted all your data, and its your fault. We did whisper into the wind three times, you should have heard it. No, there is no chance of recovery"?

You might have literally deleted people's whole businesses, companies, who employ real people, who have families, now need to figure out how to continue. Not least of which, your own. If the company survives until Christmas I will be shocked; no one can trust your company ever again - your core business is storing other people's data, and you deleted it, for many, completely without warning.

I guess people still use Mongo even after finding it doesn't achieve any property of the CAP theorem, maybe some people will keep using a database provider with a track record of intentionally deleting their paying customers' data.

There just aren't enough adjectives for astonishment to adequately describe this situation.

I hope you offer Jay Clifford some support, he's clearly been put in the awful situation of having to explain the decisions of others and deliver the awful news. If I were him, I would be in need of serious mental health support, this is an absolutely awful thing to have responsibility for without any ability to rectify.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton