Rebuilding our Electron meeting-recording engine in Swift (circleback.ai)
35 points by arguiot 3 hours ago
losteric 2 hours ago
I really struggle to get past AI writing. Aside from feeling disrespected, something about that style is just so tiring to read… the marketing style of setup and reveal, repetition, only works in small doses
hbn 20 minutes ago
The offensive part to me is thinking we should all want to read something that you don't even think is worth writing.
sebiandev an hour ago
I was just about to comment the same. It's incredibly rude to just dump AI slop on people and expect them to parse it and suffer through the grating cadence that AI writes in.
trollbridge an hour ago
I already have to read the output from a fleet of agents every day for my job. Sometimes I just want to read what a human wrote.
weaksauce an hour ago
fragmede 3 hours ago
Interesting! I'm in a similar boat, supporting windows and macOS out of one swift codebase. No MP4 issues, but it's been interesting seeing how's much code can and cannot be shared, and how much AI needs to be cajoled into writing code that's shared vs reimplementing it twice.
trollbridge an hour ago
Really? I’ve had no trouble at all directing an agent harness to simply maintain multiple UIs (in my case, Android, macOS + iOS, and a TUI, the latter mostly to ease debugging).
insane_dreamer 30 minutes ago
> This is where the macOS engine earns its complexity.
Hi, Claude.