A library with no code, no support, no implementation, no guarantees, no bugs are “fixable” without unknown side effects, no fix is deterministic even for your own target language, …
A spec may be language agnostic, but the language model depends on trained on implementations. So, do you end up with standard library implementations being duplicated, just possibly outdated with open bugs and holes and gaps and old constructs? And quality and coverage of spec implementation will vary a lot depending on your target language? And if there’s not enough conforming training it may not even follow the spec correctly? And then you change the spec for one niche language?
If it’s a spect or LLM template, then that’s what it is. Don’t call it library. In the project readme don’t delay until the last third to actually say what it is or does.
A library with no code, no support, no implementation, no guarantees, no bugs are “fixable” without unknown side effects, no fix is deterministic even for your own target language, …
A spec may be language agnostic, but the language model depends on trained on implementations. So, do you end up with standard library implementations being duplicated, just possibly outdated with open bugs and holes and gaps and old constructs? And quality and coverage of spec implementation will vary a lot depending on your target language? And if there’s not enough conforming training it may not even follow the spec correctly? And then you change the spec for one niche language?
If it’s a spect or LLM template, then that’s what it is. Don’t call it library. In the project readme don’t delay until the last third to actually say what it is or does.