upvote

points

by thrwy1994031411 hours ago |
comments
upvoteby IgorPartola10 hours ago|
next
[-]
Now that this work is done and out in the open what in theory would prevent the next generation of LLMs from ingesting it and eventually a non-Apple employee creating yet another driver “from scratch” but with the knowledge of how the hardware works acquired from an LLM or with the help of one?

Basically, aren’t we facing a situation where LLM-assisted knowledge laundering is becoming a thing?

reply
upvoteby rjsw10 hours ago|
parent|
next
[-]
Some arguments in the Apple vs OpenAI case look like they could lead to a decision on whether an LLM can wash away copyright or not.
reply
upvoteby iAMkenough10 hours ago|
parent|
prev|
[-]
Yes, as well as accountability laundering. Technofascists are loving it.

Nobody has been held accountable for AI selecting a grade school as a bombing target on the first day of America and Israel’s strikes on Iran. 100+ school girls killed, and no accountability.

reply
upvoteby ADevWithAnIdea10 hours ago|
prev|
next
[-]
Linking to another HN comment: https://news.ycombinator.com/item?id=49719480
reply
upvoteby outworlder8 hours ago|
prev|
next
[-]
Resume says : "Machine Learning Engineer".

Exactly how does that equate to knowing details of Apple's GPU implementation? Apple is a massive company.

reply
upvoteby xp847 hours ago|
parent|
[-]
The detractors around here would like to cede the absolute maximum possible territory that can be ceded to the copyright bully types, to avoid even the slightest possibility of trouble. "Did you even once enter Caffe Macs and eat a croissant? Stay 100 feet away from every FOSS project for life. Otherwise the beast might threaten us with a lawsuit."
reply
upvoteby cromka9 hours ago|
prev|
next
[-]
> All this work is tainted since the poster is ex-Apple[1].

So if I worked as a janitor at Apple, I couldn't contribute anymore?

reply
upvoteby ryandrake8 hours ago|
parent|
[-]
I’m glad I did my one Linux kernel driver contribution before I worked at Apple. What a surprise to know that I’ll never be able to contribute to it ever again.
reply
upvoteby kanwisher44 minutes ago|
prev|
next
[-]
Why do you hide behind throwaway accounts instead of just using your identity ? its harder to listen if you dont want to say who you are
reply
upvoteby userbinator3 hours ago|
prev|
next
[-]
I don't give a flying fuck.

Ignoring the idiocy of Imaginary Property is how China is winning.

It's time we caught up and then leap ahead. Everything is a derivative work.

reply
upvoteby otterley3 hours ago|
parent|
[-]
So, what do you do for a living?
reply
upvoteby Dylan168072 hours ago|
parent|
[-]
If you're going to make some kind of argument about the benefits of copyright for preserving software jobs, keep in mind this is a driver for hardware apple sells. Everyone would be better off if drivers were mandatory open source.
reply
upvoteby 2 hours ago|
parent|
[-]
deleted
reply
upvoteby nine_k10 hours ago|
prev|
next
[-]
There were and are many important pieces of Linux kernel that live out of tree; ZFS is a big example.

The problem with this driver is not licensing or code quality; I assume it's under a threat of receiving C&D letter, or maybe also a legal suit for breaking some NDA.

reply
upvoteby cromka10 hours ago|
parent|
[-]
> important pieces of Linux kernel that live out of tree; ZFS is a big example.

Including the proprietary GPU drivers. If this MacBook driver end up out of tree, so be it.

reply
upvoteby porphyra10 hours ago|
prev|
next
[-]
Very sad. I really want to get Linux on newer Apple chips working flawlessly but I can understand the legal minefield about this particular work.
reply
upvoteby kccqzy9 hours ago|
parent|
next
[-]
That’s fine. Linux upstream won’t take his code but you can for your own purposes.
reply
upvoteby SXX7 hours ago|
parent|
[-]
There is no reason Linux the Kernel upstream wont take his code. Asahi is not Linux upstream.
reply
upvoteby josephg9 hours ago|
parent|
prev|
next
[-]
The only cost was a month of llm usage. If the legal questions matter to you, you or someone else should be able to spend some tokens to redo their work in a similar way. I doubt Apple will actually care much about this. But even if they do, the worst they’ll do is get the repo taken down.

It may also be legal to do the following: 1. Have an llm read all the code these people have written and produce extensive documentation. 2. Have another llm consume that documentation and write another working driver. I am not a lawyer but I think this may fall under fair use, because reverse engineering is allowed for interoperability.

reply
upvoteby cromka10 hours ago|
parent|
prev|
[-]
Nobody does. We're only about to start settling it in courts, likely the supreme ones.
reply
upvoteby porphyra10 hours ago|
parent|
[-]
I meant I can understand the fact that a legal minefield exists.

I didn't mean that I understand the actual intricacies of the legal situation.

Sorry for my confusing wording.

reply
upvoteby xp847 hours ago|
prev|
next
[-]
> and this creates a major conflict.

Apparently. But Apple should be ashamed of themselves for that fact. What are they so afraid of? That Mac OS is so inferior to Linux that if they publish specs so that a driver can be made, that everyone will wipe Mac OS off their disks like it's Windows ME??

Once again, modern Apple is allergic to competing on their product's merits, clinging to force as though it's the only way anyone will choose them. Which is insane to me given how loyal their following is. I'm typing this shit on Mac OS right now.

Apple comes off like the most insecure corporate culture in history.

reply
upvoteby mathisfun1234 hours ago|
prev|
next
[-]
> There's also ongoing issues around Codex for this sort of thing, given Apple is suing OpenAI over stolen trade secrets

these two things have absolutely nothing to do with each other whatsoever

reply
upvoteby SXX9 hours ago|
prev|
[-]
> There is no way Linux will take that code, since people from Apple also contribute to Linux and this creates a major conflict.

I guess author can cleanup the code and try upstream it themself. Then let's see what Linus thinks of it.

reply