I find it interesting someone posted a patch to the KERNEL with a comment of "doesnt always work?" It would seem prudent to invest a bit...
I find it interesting someone posted a patch to the KERNEL with a comment of "doesnt always work?" It would seem prudent to invest a bit more time to understand why a particular thing doesn't work, for such a critical bit of code (I'm not implying I know that this is the cause or related to these new found bugs, but the article mentions it, so I'm just a little surprised).
Posted by spydum on Nov 30, 2014, 7:03 PM
Tags
Related issues
- Not sure what you suggest to do.
- Why is this not yet published on the official website and why is there no CVE?
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
hackernews (Other)
Not sure what you suggest to do.
NewWhy is this not yet published on the official website and why is there no CVE?
NewThe biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
I find it interesting someone posted a patch to the KERNEL with a comment of "doesnt always work?" It would seem prudent to invest a bit...
I find it interesting someone posted a patch to the KERNEL with a comment of "doesnt always work?" It would seem prudent to invest a bit more time to understand why a particular thing doesn't work, for such a critical bit of code (I'm not implying I know that this is the cause or related to these new found bugs, but the article mentions it, so I'm just a little surprised).
Comments (0)
No comments yet. Start the discussion.