- cross-posted to:
- linuxphones@lemmy.ca
- cross-posted to:
- linuxphones@lemmy.ca
Every line in the boot path is code we wrote. There is zero Apple code between power-on and Linux. The bootloader is ours, top to bottom. To our knowledge, no one has done this on an A13 device before.
Almost zero info, but they do sell a €150 stick with an AI slop unicorn on it. Sounds very fishy to me.
TBH, we’re going to see a lot of this shit. Documented exploits, documented hardware, documented OS, The current gen of AI tooling is pretty good at retrying tons of shit until it gets SOMETHING working. What runs will probably not be performant, and since no one wrote it or understands it, they won’t have any clue how to make it run better and that’s something that the current tooling is NOT good at.
Could people review what the AI shits out and clean it up?
To an extent. Perf is often as much about architecture as it is about code. That guy who created Adobe alternatives- all those apps are dog slow; they have to do low-quality preview renders. That’s something Adobe probably spent a few lifetimes siphoning out every last watt of power from, and it’s the reason they didn’t want to move to Linux. The app is still serviceable, but it has to degrade active quality to work at a reasonable pace. To fix that in Rust is going to be an enormous ask. There needs to be hackery and jiggery-pokery, the kind of things that aren’t documented well in training.
Maybe he can go back and have it try to figure out what Adobe is going or brainstorm ways to do it at full quality. Maybe someone will have to dive into the code, get familiar with it (hoping it’s not too confusing), and either fix the architecture, fuck with the security to let it use more base system calls, or maybe just tell another Claude session how to make it more performant.
Of course.
Seems a decent use for it then, just having it brute force corpo nonsense. Kind of a “let them fight” situation.