3 ms·
> You just need an audio buffer That alone to do right on macOS using Swift is an exercise in pain that even coding bots aren't able to solve first time right
by isodev 7mo ago
> You just need an audio buffer
That alone to do right on macOS using Swift is an exercise in pain that even coding bots aren't able to solve first time right :)
- reactordev 7mo agoI beg to differ. My agent just one-shotted a MicrophoneBufferManager in swift when asked. Complete with AVFoundation and a tap for the audio buffer. It really is trivial.
- Anonbrit 7mo agoAny chance of pushing it to GitHub? My swift knowledge could be written out on an oversized beer coaster currently, so I'm still collecting useful snippets
- reactordev 7mo agohttps://gist.github.com/gabereiser/cd8c67262717afd2539dc9c3d00d2c2f https://gist.github.com/gabereiser/cd8c67262717afd2539dc9c3d...
- hirvi74 7mo agoI've also had great results with using LLMs to pry into Apple's private and undocumented APIs. I've been impressed with the lack of hallucinations for C/C++ and Obj-C functions. I can attest that the quality in this domain has greatly improved over the years too. I am not always fan of the quality of the Swift code that my LLM produces, but I am impressed that what is often produced works in one shot, as well. The quality also is not that important to me because I can just refactor the logic myself, and often prefer to do it anyway. I cannot hold an LLM to any idiosyncrasies that I do not share with it.
- reactordev 7mo agoExactly. Even if it’s a skeleton, as long as it does “The Thing”, I’m happy. I can always refactor into something useful.