Comment by numpad0
19 hours ago
Doesn't even have to be that extreme: there is no way port placements of a Mac Mini can be mathematically derived from a plain English natural language prompt, and yet that's what they're trying to do. It's just the reality that not everything happen or could be done in literal languages. I guess it takes few more years before everyone accepts that.
There's nothing new in EE under the sun. Hasn't been for 40 years really. EE's min/max a bunch of mathematical equations. There's a lot of them, but it's not nearly as difficult as people think it is. They end up being design constraints, which can be coded, measured, and fed back into the AI.
It's not even been three years since Github Copilot was released to developers. And now we're all complaining about "vibe-coding".
Design constraints that have so many factors that people still don't use autorouters for most stuff. You're not getting it, drawing the wires isn't the hard part, understanding the constraints is.
I think we agree with that part.
I once thought software constraints were so hard a machine would never be able to program it.
But on the other hand, there are tons of circuit boards designed day after day. If it was super hard, we'd not be able to have the tens of thousands of high speed motherboards that come out year after year.
So "not everything happen or could be done in literal languages" is the part that got you?
18ghz circuits were around since 1973 was the part that got me.
Your response doesn't really add to the conversation so I'll stop here.