[–] 1 point 4 days ago* (1 child)

The link I posted is to the Curl maintainer's own blog, in which he wrote a follow-up to his earlier post about shutting down their bug bounty program. See also this more recent blog post by the maintainer of Curl, in which he writes that

I personally don’t refer to [vulnerability reports created with the help of AIs] as AI slop because the reports are typically accurate and correct, even if much too wordy. I think “slop” implies that it is wrong, misleading or otherwise bad content.

  • source
  • parent
  • context
  • [–] 4 points 4 days ago (3 children)

    According to the lead Curl developer, the quality of LLM generated reports has gone up quite a lot, to the point where the number of high quality reports is the problem, rather than the number of slop reports: https://daniel.haxx.se/blog/2026/04/22/high-quality-chaos/

    However, I doubt that their bug bounty program is ever coming back. As you say, that'll just attract the people looking for a quick buck, and those are unlikely to care about the quality of their reports

  • source
  • parent
  • context
  • [–] 4 points 1 week ago

    Thank you for the answer!

    I have not previously heard Meson described as a reinvention of Cmake or a CMake clone, nor that it was meant to be. I would think that Meson being as opinionated as it is, including for example the fact that it does not and will not support user-defined functions, precludes it from being a CMake clone. It seems instead to be a build-system with a rather different philosophy and feature-set compared to Cmake. But if that philosophy or that feature-set does not match your needs, then there's obviously no reason to pick it over CMake

  • source
  • parent
  • context
  • [–] 1 point 1 week ago* (2 children)

    Out of curiosity, why do you consider CMake to be the better choice compared to Meson?

    Personally I landed on Meson a few years ago, from what I remember chiefly due to simply not liking CMake's DSL and finding Meson easier to work with, despite needing to target a pretty old version for the sake of compatibility. Though Meson is definitely not perfect either; it's highly opinionated, and for example only recently got support for custom build targets putting stuff in sub-directories (as I discovered while writing this comment), so I'll personally be stuck with my workarounds for a good while longer

  • source
  • parent
  • context
  • [–] 2 points 2 weeks ago* (1 child)

    As soon as uv provides an alternative implementation so you can just run uv run --but-fast I think it will become popular.

    You can already do uv run -p pypy and uv run -p graalpy to automatically download and use those versions of Python.

  • source
  • parent
  • context
  • [–] 37 points 2 weeks ago* (2 children)

    For anyone curious about the number of bugs introduced in each kernel release, LWN.net has a plot of Bugs fixed and introduced in each kernel release.

    However, it has the obvious limitation that recent releases will appear to have fewer commits introducing bugs, simply because kernel developers haven't had as much time to find and fix the bugs introduced in those releases. So it'll be a while before we can actually see the consequences (positive or negative) of more widespread LLM usage by kernel developers

  • source
  • [–] 8 points 3 weeks ago* (last edited 3 weeks ago) (5 children)

    Recently had to develop a Python project, the tests took at least ten seconds to start each single time. This is while I made over a hundred tests for my module and re-ran them after every change.

    Python is dog slow, but if each of your tests are taking 10 seconds to start (not even run!), then something is catastrophically wrong with your setup. For comparison, for one of my projects, it takes a total of 12 seconds to run nox on a clean slate, which involves setting up venvs for five major versions of Python, installing the package and its dependencies in each, and finally running the 1500 test test-suite five times

  • source
  • parent
  • context
  • [–] 20 points 3 weeks ago (12 children)

    What about the fact that runtime startup alone auto-disqualifies python for all short-lived process use-cases?

    While Python's start-up time is a lot slower than a corresponding compiled program, in most cases it's not slow enough to matter even if the process itself is short-lived:

    $ hyperfine 'python3 -c "pass"'
    Benchmark 1: python3 -c "pass" (412 runs)
                    mean     ±       σ          min     …     max
      Wall Time      7.1 ms  ±     0.2 ms       6.7 ms  …     8.4 ms
      Memory         9.4 MiB ±     0.1 MiB      9.1 MiB …     9.5 MiB
    

    If you are running a small program so often that this kind of start-up time matters, then the loop should probably already be implemented in the program itself. In line with the article's thesis

  • source
  • parent
  • context
  • [–] -1 points 1 month ago (1 child)

    But you really should be writing those tests regardless of whether or not you or an LLM ends up writing the actual code. That helps ensure that the code actually does what you think it does, and prevents bugs or unintended changes in behavior from sneaking in later when something changes

  • source
  • parent
  • context
  • [–] 3 points 1 month ago

    Granted, I’ve seen one or two articles saying that AI helped find real software bugs, but what’s the ratio there, 1:500 for useful/useless AI bug reports?

    It's worth distinguishing between LLM generated bug-reports submitted by randos, and developers themselves using LLMs to look for bugs in their software.

    My own experience, with my own code-bases, is that the LLM I use is extremely good at finding real flaws in my code. It'll also nitpick a lot, but it has has become better at triaging issues than it used to be, so that kind of thing is easy to ignore.

    Because of that, having an LLM take a look at my code before I push it has become another QC step, along with running tests, linters, and formatters. The end result is higher quality software

  • source
  • parent
  • context
  • view more: next ›