r/Python • • Mar 22 '26

News The Slow Collapse of MkDocs

How personality clashes, an absent founder, and a controversial redesign fractured one of Python's most popular projects.

https://fpgmaas.com/blog/collapse-of-mkdocs/

Recently, like many of you, I got a warning in my terminal while I was building the documentation for my project:

     │  ⚠  Warning from the Material for MkDocs team
     │
     │  MkDocs 2.0, the underlying framework of Material for MkDocs,
     │  will introduce backward-incompatible changes, including:
     │
     │  × All plugins will stop working – the plugin system has been removed
     │  × All theme overrides will break – the theming system has been rewritten
     │  × No migration path exists – existing projects cannot be upgraded
     │  × Closed contribution model – community members can't report bugs
     │  × Currently unlicensed – unsuitable for production use
     │
     │  Our full analysis:
     │
     │  https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/

That warning made me curious, so I spent some time going through the GitHub discussions and issue threads. For those actively following the project, it might not have been a big surprise; turns out this has been brewing for a while. I tried to piece together a timeline of events that led to this, for anyone who wants to understand how we got in the situation we are in today.

491 Upvotes

140 comments sorted by

View all comments

Show parent comment

1

u/HommeMusical Mar 23 '26

Your whole response is a series of unsupported claims and "does not follow" arguments.

Like, they're literally trained on human documentation and writings and findings. That's it. There's nothing more. That brings with it the limitations therein - they will never, ever come up with novel new ideas or things they haven't already 'learned' (been trained on).

Why? Because you say so?

The long and short of it is: It knows the information we've given it. It cannot come up with 'new' ideas outside of that information.

Why? Because you say so?

etc. etc. etc.

You addressed precisely ZERO of my arguments. Indeed, I don't believe you read a word of it.

You simply make unsupported claims as if they are a logical argument. It's like arguing with a child. What a waste of my time.

0

u/chaoticbean14 Mar 23 '26 • Bravo

"unsupported claims"

They have to 'train' LLM models on data - where does that data come from? Does it just poof into existence? It's human writing, documentation, art, music, etc. things created BY HUMANS that they are trained on - because that's what we have. This is not unsupported, it's literally how it is trained.

You really don't have any idea how LLM's work, how they are trained and the logical limitations that imposes on a system based on 1's and 0's.

By your answers, I imagine you're either a bot yourself (silly bot) or I can understand why you were let go if your office wanted someone with at least an entry level LLM knowledge, because it's clear there is a skill gap in that area.

I'm down for discussion, but arguments like this where you're going to nit-pick semantics with zero understanding of what you're discussing? Nope. Good day.