81–90 of 397 posts
This is really neat, I'm glad it worked. This is atrocious C code.
**Decision**: Use C for kernel interactions, Zig for pure logic only.
Earlier quoted context omitted.
I think in the future (in 10 years?) we are going to see a lot of disposable/throwaway software. I don’t know, imagine this: I need to buy tickets for a concert. I ask my AI agent that I want tickets. The agent creates code on the fly and uses it to purchase my tickets. The code could be simple curl command, or a full app with nice ui/ux. As a user I don’t need to see the code. If I want to buy more tickets the same…
Or, and hear me out here, you go to the existing site or app which sells concert tickets, press the purchase button, and then you have your tickets. Like what are we even doing here...
It’s like we usually say: companies should focus on their core value. And typically the ui/ux is not the core value of companies.
Earlier quoted context omitted.
The primary reason why it worked is because Claude could rip off the Linux driver. Without any prior work to rely on, how will the AI figure out proprietary hardware?
GPL is not a patent. It covers the work and _derivatives_; it does not cover ideas or general knowledge. The chip in question has docs. I fully expect that Claude wrote code that does not resemble that of the driver in the Linux tree. TFA is taking on some liability if it turns out that the code Claude wrote does largely resemble GPL'ed code, but if TFA is not comfortable with the code written by Claude not resemblin…
In this case, they didn't really work from the chip's published documentation. They instead ultimately used a sorta-kinda open-book clean-room method, wherein they generated documentation using the source code of the GPL'd Linux driver and worked from that.
That said: I don't have a dog in this race. I don't really have an opinion of whether this is quite fine or very-much not OK. I don't know if this is something worthy of intense scrutiny, or if it should instead be accepted as progress.
(It is interesting to think about, though.)
Earlier quoted context omitted.
I think in the future (in 10 years?) we are going to see a lot of disposable/throwaway software. I don’t know, imagine this: I need to buy tickets for a concert. I ask my AI agent that I want tickets. The agent creates code on the fly and uses it to purchase my tickets. The code could be simple curl command, or a full app with nice ui/ux. As a user I don’t need to see the code. If I want to buy more tickets the same…
This is also where I think we end up. If the behavior of the system is specified well enough, then the code itself is cheap and throwaway. Why have a static system that is brittle to external changes when you can just reconstruct the system on the fly? Might be quite awhile before you can do this with large systems but we already see this on smaller contextual scales such as Claude Code itself
The thought of converting an app back into a spec document or list of feature requests seems crazy to me.
Earlier quoted context omitted.
I don’t think Apple is any different than any other vendor who doesn’t bother releasing Linux drivers? support for most devices depends on the community creating them no? If you’re a macOS fanboy presumably you don’t care about Linux support.
>I don’t think Apple is any different than any other vendor Read my previous comment again!! If you buy a genuine display and install it, it won't work because Apple locks the hardware ID via firmware. It must be installed by Apple only. No other vendor does that, the Linux community always found its way to get a non-supported hardware working. Windows until recently with the AI slope, was the only major OS used ever…
Apple publishes repair guides for this (e.g., https://support.apple.com/en-us/120768) as does iFixit. Genuine parts are available for purchase and tools are available to rent by individuals (see https://support.apple.com/self-service-repair, which specifically mentions display replacement). Skill and patience are required; replacement by Apple is not.
> Instead of continuing with the code, I spawned a fresh Pi session, and asked the agent to write a detailed specification of how the brcmfmac driver works Planning markdown files are critical for any large LLM task.