Ask HN: Ten Yrs from now, when only AI codes, what's the stack?
4 comments
[deleted]
At that point you wouldn't care what the ingredients were.
I guess we go back to basics since the main reason to use frameworks and stacks are the benefits of like, consistent structure, knowledge shared across teams, hiring people with prior experience from other jobs. Those don't matter at all to AI.
What does matter is poisoned dependencies, it might end up better to have AI generating bespoke routing, data/state stores, ORMs etc that would be redundant for you to get distracted with today. Humans can barely police dependencies today when humans are producing the dependencies and curating their use so probably a 10x bigger problem in a decade.
I guess we go back to basics since the main reason to use frameworks and stacks are the benefits of like, consistent structure, knowledge shared across teams, hiring people with prior experience from other jobs. Those don't matter at all to AI.
What does matter is poisoned dependencies, it might end up better to have AI generating bespoke routing, data/state stores, ORMs etc that would be redundant for you to get distracted with today. Humans can barely police dependencies today when humans are producing the dependencies and curating their use so probably a 10x bigger problem in a decade.
Why have a stack, machine-code all the way down baby
IA
What would be the stack and why? Do we still have 1000 JS frameworks?