4 ms·
They explain it in the article but I'll paraphrase here. Historically there wasn't a single good answer/method that could be applied universally to many of the
by MadnessASAP 2y ago
They explain it in the article but I'll paraphrase here.
Historically there wasn't a single good answer/method that could be applied universally to many of the problems. Hence user selectable and configurable plugins to allow the user to experiment for what worked best for them.
That is no longer the case, the project has matured to the point that a optimal choice is known meaning that the existing plugin system only provided the user with a footgun. This they folded plugins and their developers into the codebase and built a database of known optimal configurations.
- happymellon 2y agoI read the article. You didn't read my comment. My comment was actually curious about the overhead of rewriting the plugins to roll them in wondering how much effort that was.
- MadnessASAP 2y agoI wouldn't imagine it was that much, I would suspect the API remains largely unchanged, just the library code gets compiled in rather then being loaded at runtime. I read your comment as more not seeing the benefit of the change.