As a result you have to look at what they share about themselves to infer where they're going with things, because they never explicitly state it. All traits amplified for the worse when people use chat bots too much, in my experience.
Scrolling to the end, they write:
> In 2005 a dozen version control systems fought to replace Bitkeeper, and the winner ended up ruling software development for two decades. Nobody in that race predicted that the decisive factor would be a hosting site with a social network on top.
They had a VCM start-up around their own technology, then Git displaced all other technologies, and then Github ate everyone's lunch. So the first revolution not-so-coincidentally overlaps with the time they ran a SCM startup, and they ignore anything that happened before they entered the space. Funny that.
So the implicit context is the business case and programmer culture around VCM systems.
Meaning the second revolution is anything that challenges Git and Github.
They also keep bringing up gigantic mono-repos and how Git can't handle the scale at which AI increases the amount of code bloat or commits.
So what I read between the lines is that they believe that there are enough people who don't want to actually address the automated hyperscaled Wirth's Law in the room, and are willing to pay services and technology to adapt around it instead.
That's their new business case that will power the second "revolution".
Which sounds horrifying to me, and the worst part is that I can actually see it happening if this AI bubble doesn't pop fast enough.
I don't understand why everyone keeps saying "AI" can write code and somehow the rest of the world can't keep up when we haven't even solved a more basic problem that "AI" itself can't keep up with the code it writes. Claude on the web has to search and scan to find the relevant parts and for whatever reason there is a size limit to how much context I can give to claude and it is laughably low. Shouldn't we be trying to see if it can keep up with itself first? Also not all project files fit in the "context" so once you are in search mode anyway, why is the limit so arbitrarily small? Why not allow at least about 1GiB of plain text? Claude tells me 1 GiB is 250 million tokens and it is too much for current capacity but I thought the whole point of project files was not all of it is in the context window or whatever. It says it is in search mode anyway... So only search for the relevant bit and put only that in the context. You can limit your search to a particular submodule or something but still have broader context where required
I also doubt very much that the average monorepo is bigger than the linux kernel. While the latter is a single software as things go, it contains quasi independent subsystems. And those repos don't usually have a merge flow that is as smooth as the Linux kernel. If you have chaotic process, then the result won't be very good and it's not git's fault.
So, datacenters will fix that.
Banks, airlines, power infra, and other high-stakes customers got computerized in the 60s and 70s. IBM still holds a chunk of that market. Microsoft and Google are not going anywhere. So I guess all that slop will serve something less critical than all of the above.
Blog authors need a straight up TL;DR because I ain't reading all of that.
I think that's part of why tiktok and yt shorts really took off. It's so short that if you realize it's bad and move on then your wasted investment in terms of time and energy was negligible. (Times 200 that's a different story but signal-to-noise is still high enough that people accept this.)
For the next time, instead of scrolling, you can just press the little "-" next to a post which collapses it and its whole subtree. Out of sight.
Besides, I explicitly stated that I read 2/3 of the article. How is that "low attention span"? And I didn't just bash it, I formulated what I find missing in it. Do you have answers to those questions? And how does asking such questions indicate "reading difficulties"?
It's quite fascinating that if my comment is so appaling to you, why you'd take the time to respond. I thank you for that though.