And thanks to hiring 1,000 new people to patch it, now they have N * 1.5 vulnerabilities!

I meant infested, not invested

*You* would not want this.

However on endpoints vaguely related to your work, your employer *loves* excuses to give Microsoft money to invest as many endpoints as possible.

When the US was attacked, we sent our children to die in one of your foreign wars.

When WE were attacked, the largest war in the continent since World War II, you abandoned us - even witholding things that cost you *literally nothing*, like intel to help intercept drones and missiles targeting civilians - and switched to instead threatening to attack us as well, helping pick us apart piece by piece.

  Do not act surprised when you get seen as duplicitous snakes and we take action to separate ourselves from your levers of pressure.

Nowhere in this do I see how maintaining the history in this manner even benefits AI. I haven't seen evidence that it can benefit from an insanely over-granular change history.

This is not debating the volume of code, it's the granularity of delivering it as tiny 'changesets'. Just because you *can* create a system that can partition changes into 3 second intervals does not mean there's any value for machine nor human in doing so.

To start, the condescension is hardly helpful.

The point stands, you have to consider the audience for the change tracking. How much granularity is really useful even for the AI models themselves to digest? Certainly no human will digest, but I also don't think the AI is going to be prioritizing putting hundreds of thousands of change history entries into the context window on the off chance that it is relevant to the task at hand.

It seems like a solution to pretend around change management while abandoning any actual use of change management, by human or machines.

O Lord of the Abyss, Prince of Darkness, Morning-Star, please hear my cry: I invoke thee, Lucifer! Turn your gaze toward the Vatican's operating rooms! Guide the surgeon's scalpel with your claws! Burn the tumors from the Holy Father's chest with the infernal fires of Hell! Cast your curses upon any bacterium that may seek to cause opportunistic infection! In the darkness I beseech thee.

Hail Satan, please save the Pope, Amen.

It's cheap and easy to audit OSS for malicious code with AI these days.

It's not really about Microsoft. Increasingly, Europe sees the US as a potential threat who blackmails allies, even a potential invader, rather than an ally.

Literally just yesterday the US shut off intel-sharing to Ukraine (which mainly helps with targeting incoming drones) and blocked all Starlink terminals in Ukraine moving faster than 100kph (e.g. terminals on air-defense interceptor drones), both in effect dramatically hurting Ukraine's ability to defend against Russia's nightly drone waves - all in order to pressure Ukraine into stopping striking Russian oil refineries while Trump seeks to buy more Russian oil and Russia keeps strikig Ukraine's energy infrastructure.

We all know that the US could do this sort of stuff to any of us. We have to move US companies out of our critical paths.

Once upon a time, when the US called for aid after 9/11, Europe stood up. More Danes died per capita fighting in Afghanistan, in a war that was not their own, than Americans did. This year, Denmark was rapidly rushing explosives and bags of blood to Greenland to prepare for firefights against invading US forces.

All of Europe got the message. We're not dining with friends - we're on the menu.

Though in that scenario, it seems bad or useless for the AI as well, as the bloated change history is a waste of context window. Unless they just ignore it in which case what was the point in bothering.

But perhaps it is just another attempt to normalize "human shouldn't be in the loop" mindset, the new toy is but an excuse to say you *should* be having a codebase that is being changed every couple of seconds without bound.

I just cannot wait for that day. When people have a least a *little* less incentive for certain folks to butt in on other people's jobs and tell them how it should be done, despite never even doing nor using an AI to do said job in a serious capacity.

This story triggered a colleague to tell me that I need to stop using git, despite never having used *any* version control scheme nor even using an AI to generate code, just super armchair software development. I do not understand that mindset of people that invested in the nitty gritty of software development without the will to actually do software development.

A changeset history is only so useful compared to analysis of the code as it is. Even pretty large context windows need prioritization. I would think an overly granular changeset history would be a really low prioriity.

Compared to more aggregated changes into fewer changesets, where the history would be probably more digestable, even for AI consumption.

We can't actually know if it is 'actually quite good', because we have only their own self-assessment to go on.

No way to debate how it compares with git partial/shallow clones in broader circumstances. They don't want to share it, they just want to use the concept to fluff their image. It might be amazing, it might be trash, impossible to say anything substantial based on this.

The issue is the situation isn't binary.

Linus comes along with an attempt at nuance and suddenly all sorts of high-slop vibe coders think they are just like Linus.

I know a team that has gone very hard on slopping it up AI, though they just had a flamewar where the AI bros bitched that the more careful people were holding them back by insisting on human review and rejecting merge requests where the human didn't understand what they were submitting.

The thing is, this team was already pumping out shit code for years, so in their case the AI might actually be compelling. Infested by PHB thinking of 'hire many people in random geography, to change each year as different geographies are proven to be shit when you only pay bottom of the barrel'. They have been rotating cheap labor forever hoping for the magical geo where the cheapest people are still skilled (no such geography exists, the bottom of the barrel in any geo is trash). So AI is next on their search.