Hacker News new | ask | show | jobs
by pjmlp 123 days ago
It is hardly any different from,

C Source code => Tradicional UNIX C compiler => ASM => object file

Now everyone is doing

AI tooling => C Source code => Tradicional UNIX C compiler => ASM => object file

For all pratical purposes, just like using a language like Nim, the workflow exposed to user can hide the middle steps.

Then there is the other take, if you start using agents that can be configured to do tool calling, it is hardly any different from low code applications, doing REST/GraphQL/gRPC calls orchestrated via flow charts, which is exactly what iPaSS tooling are offering nowadays, like Workato, Boomi,...
1 comments
bestouff 122 days ago
> Now everyone is doing > > AI tooling => C Source code => Tradicional UNIX C compiler => ASM => object file

Certainly not. I'm using AI to write Rust, the compiler is way better at telling the AI it goofed completely, and the resulting code (once the AI managed to get rid of errors/warnings) has a much better chance of actually working well.

link
pjmlp 122 days ago
The use of C was only an example, and I can bet that AI can also goof Rust code that goes through the compiler if that is your argument.

Unless you now tell me that you drive your AI generation code with full coverage unit tests manually written by you.

link