• Midnight Wolf@lemmy.world
    link
    fedilink
    English
    arrow-up
    46
    arrow-down
    1
    ·
    4 hours ago

    AI Cartel: we will buy all your stock

    Memory Cartel: yaaaay!

    MC: but now nobody is building computers, hurting our storage business :(

    AC: we gotchu fam, we will just make our systems outrageously system demanding, killing components and driving sales

    MC: yaaaaaaaay

  • neon_nova@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    43 minutes ago

    Is there a way to mitigate this while still using codex like moving my project to an external drive I don’t care about?

    Is it better to switch to Claud code?

  • tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 hours ago

    If you’re on Linux and aren’t particularly fussed about any issues stemming from power loss, you can probably run it under eatmydata and it’ll disable SQLite calls to fsync().

  • adarza@piefed.ca
    link
    fedilink
    English
    arrow-up
    11
    ·
    4 hours ago

    eating their own dog food, are they?

    they’ll have to hire an actual developer to fix it.

  • DevDave@piefed.social
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    6
    ·
    4 hours ago

    it’s weird who gets reported for this stuff.

    There was a game that released not too long ago that was spamming the same message to it’s log file in 500 millisecond intervals doing a constant stream of write and flush to disk the entire time the game ran.

    silence.

      • eleijeep@piefed.social
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        2
        ·
        3 hours ago

        Can you explain how you came to that conclusion? I don’t know what game it was and how many copies it sold, nor how many Codex users there are, but I assume you already know those details?

        • cecilkorik@piefed.ca
          link
          fedilink
          English
          arrow-up
          8
          ·
          2 hours ago

          500 milliseconds is an eternity in computer time. Doing a 10KB write (very generously large for a logfile) write every 500 milliseconds is something it could do continuously for about 1,000 years before it used up the write capacity of an SSD.

      • DevDave@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        3 hours ago

        cue the scene from Airplane 2 where the Steward explains they have been knocked of course by just a “tad”