Comment by throawayonthe
21 hours ago
can you explain how? with a compiler you can rely on the adage "it's never a compiler bug" (until it is! and then you can fix it)
how can a local LLM with an open source agent harness provide the same trustworthiness?
> ... then you can fix it
I recall working on a project that used (MSVC) VC++ and a coworker found a bug in the compiler. We reported the issue to Microsoft and they eventually patched it.
You may find yourself arguing explicitly for open source dev tools if you continue down this line. There are many commercial cases where "you can fix it" does not apply to the dev toolchain and you will find yourself reliant on a provider. At that point, the trustworthiness of "compiler provider" and "local LLM provider" is the pertinent discussion (e.g. provider vs. provider instead of LLM vs compiler).
> There are many commercial cases where "you can fix it" does not apply to the dev toolchain and you will find yourself reliant on a provider.
That’s only on the hobbyist level. On the enterprise level, there are lots of contracts involved that requires speedy bugs correction.