he/they

  • 102 Posts
  • 1.01K Comments
Joined il y a 3 ans
cake
Cake day: 2 février 2024

help-circle


  • Quick follow-up, for the sake of furthering my argument:

    Baldur, whilst talking about the aforementioned loss of FOSS surplus, laid out a worst-case scenario, where a vicious cycle collapses the FOSS ecosystem:

    1. Declining surplus and burnout leads to maintainers increasingly stepping back from their projects.

    2. Many of these projects either bitrot serious bugs or get taken over by malicious actors who are highly motivated because they can’t relay[sic] on pervasive memory bugs anymore for exploits.

    3. OSS increasingly gets a reputation (deserved or not) for being unsafe and unreliable. [This drives away users as a result.]

    4. That decline in users leads to even more maintainers stepping back. [return to step 1]

    As a consequence of the slop-nami, I’d argue the perfect conditions for this vicious cycle have already emerged:

    1. The slopnami has done plenty to exacerbate existing burnout in current maintainers - slop bug reports, scrapers and AI bros DDoSing services, AI bros in general and the myriad other negative externalities of this bubble have been utterly draining to deal with.

    2. As (indirectly) mentioned before, the slopnami has given a variety of serious bugs and security issues - rsync’s broken backups, the rise of slopsquatting and prompt injection attacks, Linux’s recent race condition mishap, the list goes on.


  • There’s also a part in the denouement where he says a possible solution to improving slop code quality and safety standards is uploading the code to public repositories so similarly inclined people can engage with it

    Which assumes people actually want to deal with slop code. An assumption that can be proven wrong by simply looking at the slopnami’s effect on the open source ecosystem. Speaking of which:

    which, I don’t know, seems kind of familiar if you’ve been a programming adjacent for two seconds. But then you’d also be aware what the slopnami is already doing to the open source ecosystem.

    Honestly, I’d be willing to bet good money on the ecosystem’s collapse at this point - the slopnami has tanked software quality across the board, the plague of scraping has made sharing source code deeply unattractive, the flood of LLM bug reports has crippled FOSS’s ability to find and fix bugs/vulnerabilities (which combos nicely with LLMs increasing bugcounts), and, as Baldur’s noted, the labour surplus FOSS relied upon has gone down the shitter.

    On top of that, senior devs are burning out and deciding to GTFO en masse, and junior devs are getting deskilled, burnt out and/or laid off, crippling FOSS’s ability to replace any maintainers they lose.