• 0 Posts
  • 54 Comments
Joined 5 months ago
cake
Cake day: February 4th, 2026

help-circle






  • Yep, people were reporting that it was marking code they wrote by hand as “Coauthored by Copilot.”

    There are some comments on the original pull request, such as:

    ringoz commented last week
    I am not using copilot, I have “chat.disableAIFeatures” and co-authored by copilot still gets inserted into commits.

    I also thought that this was interesting, from the above article:

    Earlier this week, Vasyura shared an update on the “co-authored by Copilot” issue. The Microsoft engineer said the forced co-authorship resulted from a bug in the code that Redmond employees did not encounter in their testing environment. The default AI attribution was eventually disabled, but is now returning in a different – hopefully less disruptive – form.


  • “These materials aren’t just operating system releases in the traditional sense. In several cases, the listings represent point‑in‑time working states and hand-written notes, preserved by Tim Paterson himself. Think of them as a printed commit history of a Git repository."

    No one’s going to be using these releases for real work. However, they’re still remarkably instructive for anyone who wants to understand how operating systems were structured on first‑generation 8086 hardware. DOS 1.0’s small size and feature limitations make it a comprehensible codebase that can be understood almost end‑to‑end, especially compared to today’s sprawling operating systems.

    As Microsoft stated, “The listings include sources to the 86-DOS 1.00 kernel, several development snapshots of the PC-DOS 1.00 kernel, and some well-known utilities such as CHKDSK. Not only were these assembler listings, but there were also listings of the assembler itself! This work offers rare insight into how MS-DOS/PC-DOS came to be, and how operating system development was done at the time, not as it was later reconstructed.”



  • Cloudflare has revealed it will farewell 1,100 staff, due to its current and future use of AI.

    In a blog post that oozes Orwellian “doublespeak”

    …this entire article’s premise is based on the “doublespeak,” though? You are literally pumping AI fear and hype based on a company’s blog article because it benefits you.

    This is a plain old layoff, just like all the others. CNBC talked about it last October. The LA Times talked about it in March of this year.

    It’s not hard to understand if you don’t benefit from AI rage bait like The Register does.

    Hack “journalists” like this are the reason the AI hype won’t go away. He’s too stupid to read between the lines or understand that he’s a huge part of the problem.

    The Cloudflare CEO even contradicts the “it’s AI, I’m telling you” narrative, right in the same article:

    “We have seen that there are roles at Cloudflare that are not the roles we need for the future,” Prince responded. “Just because you are fit does not mean you cannot get fitter. Over the last six months especially, the productivity gains from the people directly talking to customers and directly creating code have been incredible, and a lot of the support roles behind them are not going to be the roles that drive companies going forward.”

    Doesn’t matter though, The Register can squeeze another AI layoff article in there to get people riled up!








  • The real reason they cite is also quite interesting. Twice as many leased electric vehicles are coming to market.

    Analysts attribute the surge to a glut of hundreds of thousands of cheap pre-owned EVs that were purchased on leases in the early 2020s and which are now returning to market as those leases expire. According to credit bureau Experian, EVs will account for 15 percent of all off-lease vehicles at the end of this year, up from 7.7 percent in the first quarter.