{"id":104577,"date":"2025-12-02T01:47:25","date_gmt":"2025-12-02T01:47:25","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2025\/12\/02\/zig-quits-github-gripes-about-microsofts-ai-obsession-the-register\/"},"modified":"2025-12-02T01:48:28","modified_gmt":"2025-12-02T01:48:28","slug":"zig-quits-github-gripes-about-microsofts-ai-obsession-the-register","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2025\/12\/02\/zig-quits-github-gripes-about-microsofts-ai-obsession-the-register\/","title":{"rendered":"Zig quits GitHub, gripes about Microsoft’s AI obsession \u2022 The Register"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

The Basis that promotes the Zig programming language has stop GitHub resulting from what its management perceives because the code sharing web site’s decline.<\/p>\n

The drama started in April 2025 when GitHub consumer AlekseiNikiforovIBM began a thread<\/a> titled \u201csafe_sleep.sh not often hangs indefinitely.\u201d GitHub addressed the issue in August, however didn\u2019t reveal that within the thread, which remained open till Monday.<\/p>\n

\n

The code makes use of one hundred pc CPU on a regular basis, and can run eternally<\/p>\n<\/blockquote>\n

That timing seems notable. Final week, Andrew Kelly, president and lead developer of the Zig Software program Basis, announced<\/a> that the Zig challenge is shifting to Codeberg, a non-profit git internet hosting service, as a result of GitHub now not demonstrates dedication to engineering excellence.<\/p>\n

One piece of proof he provided for that evaluation was the \u201csafe_sleep.sh not often hangs indefinitely\u201d thread.<\/p>\n

“Most significantly, Actions has inexcusable bugs<\/a> whereas being completely neglected<\/a>,” Kelly wrote. “After the CEO of GitHub said to ’embrace AI or get out’<\/a>, it appears the lackeys at Microsoft took the trace, as a result of GitHub Actions began ‘vibe-scheduling’ \u2013 selecting jobs to run seemingly at random. Mixed with different bugs and incapability to manually intervene, this causes our CI system to get so backed up that not even grasp department commits get checked.”<\/p>\n

Older and deeper<\/h3>\n

Kelly\u2019s gripe appears justified, because the bug mentioned within the thread seems to have popped up following a code change<\/a> in February 2022 that customers flagged in prior bug reviews.<\/p>\n

The code change changed cases of the posix “sleep” command with a “safe_sleep” script that didn’t work as marketed. It was supposed to permit the GitHub Actions runner \u2013 the appliance that runs a job from a GitHub Actions workflow \u2013 to pause execution safely.<\/p>\n

\n