←back to thread

We're Joining OpenAI

(www.alexcodes.app)
192 points liurenju | 3 comments | | HN request time: 0.765s | source
1. yahoozoo ◴[] No.45120563[source]
So companies like this one are being acquired because they just have really good/niche system prompts? I mean, they all use the same models as everyone else, right?
replies(1): >>45120662 #
2. xwowsersx ◴[] No.45120662[source]
I'm speculating here, but my guess is that the urgency for OpenAI isn't that the Alex team has a "secret prompt." It's that they've already done the heavy lifting to make LLM coding assistants actually usable in a domain (Apple platforms) where OAI doesn't have integrations yet.

Acquiring them gives OAI:

- ready-made team that understands the IDE plumbing and the developer UX at a deep level

- head start in a platform ecosystem that's hard to crack

3. team that knows how to push the models into productized, developer-ready experiences

So it's not the prompts. It's engineering the scaffolding and UX around the model so it feels like magic to the user. That's what OpenAI is buying.

Also possible that Alex solved a lot of UX and integration challenges that could translate to other Apple contexts (productivity apps, design tools, even consumer-facing AI on macOS/iOS).

Without having used Alex myself (I don't do iOS or macOS development), I would guess that all the retrieval, context slicing, editor integration yada yada that they've built aren't necessarily unique to coding. Same scaffolding could support things like AI-driven writing, design, or general productivity in an Apple-native way.

replies(1): >>45120871 #
3. elpakal ◴[] No.45120871[source]
could just be the git/apply changes functionality they’re interested in. obviously speculation