Earlier quoted context omitted.
Because the problem has almost no value unto itself. The clay statement of navier stokes is not relevant to how CFD is done in practice. It's about what is non verifiable versus verifiable. The same way it produces "slop" code (which, if you give it test cases, will be 100% correct), it also produces "slop" math. Code that serves a business function, it's ok if its slop. Math that serves directly a business function…
> Code that serves a business function might as well be slop. Math that serves directly a business function also can be slop. Both of these are simply incorrect - serving a business function means it's valuable to that function.
I meant what you're saying. That it's OK if it's slop if it serves a business function.
Edited