Earlier quoted context omitted.
ideally, the software produced should include the latest security patches. If the model prefers a version of Ruby or node with an RCE, I guess you can burn tokens to teach the model how to avoid the introducing the vulnerability into your code? That feels quite tedious and token inefficient..
I'm sorry, but.. are you being serious? Yes. Yes. The only way one can write secure software is by always using the latest SOTA model. Anything else is inefficient and vulnerable. I hate this platform
Has writing secure C really changed that much? Lots of the world still writes in C99, 27 years old at this point. I think they can use a 9 month old AI model is they want.