←back to thread

The barriers to AI engineering are crumbling fast

(blog.helix.ml)
250 points lewq | 4 comments | 14 Nov 24 14:56 UTC | HN request time: 0.346s | source
Show context
amelius ◴[14 Nov 24 15:05 UTC] No.42136821[source]▶
Soon enough we'll have AI that is just integrated into the OS.

So individual apps don't need to do anything to have AI.

replies(1): >>42137491 #
1. michaelmior ◴[14 Nov 24 15:57 UTC] No.42137491[source]▶
What does it mean for an app to "have AI"?
replies(3): >>42137604 #>>42139895 #>>42139987 #
2. SteveSmith16384 ◴[14 Nov 24 16:10 UTC] No.42137604[source]▶
If it makes any kind of decision whatsoever (like an "if" statement), slap the word AI on it.
3. amelius ◴[14 Nov 24 19:05 UTC] No.42139895[source]▶
Think of it as another human having access to the keyboard, mouse and the screen buffer.
4. NitpickLawyer ◴[14 Nov 24 19:13 UTC] No.42139987[source]▶
At a very minimum I'd say they'll have a way to "chat" with the apps to ask questions / do stuff. Either via APIs that the OS calls or integrated in the app via whatever frameworks will rise to handle this. In 5 to 10 years we'll probably see this. At a very minimum searching docs and "guide" the users through the functionality / do it straight up when asked.

Basically what chatgpt did for chatbots, but at app level. There are lots of apps that take a long time to master. But the average joe doesn't need to master them. If I want to lightly edit some photos, I know photoshop can do it, but I have no clue where that specific thing is in the menus, because I haven't used it in 10 years. But it would be cool to type in a chat box "take all the pictures from my sd card, adjust the colors, straighten the ones that need it, and put them in my Pictures folder under "trip to the sea". And then I can go do something else for the 30-60 minutes it would have taken me to google how to do all of that, or script something, etc.

The ideea of an assistant that can work like that isn't that far-fetched today, IMO. The apps need to expose some APIs, and the "os" needs an language -> action model capable enough to handle basic stuff for average joes. I'd bet good money sonnet3.5 + proper APIs + a bit of fine-tuning could do it today for 50%+ of average user cases.