Nobody said they are 1-to-1 compatible. Also, ideally lazy loading should happen on the plugin side instead of putting it on every user to configure, since neovim natively basically has everything needed for plugins to do the lazy loading of heavy parts[1] and if something is missing it probably is better to add it the hooks for it upstream in neovim instead of the plugin manager so it also works for personal config/plugins.
But as indicated by my comment in the specific case for lazy loading, the plugin manager is the wrong place to have it. Regarding its other features I am not sure most of them need to be part of the plugin manager either (at least from the "plugin spec" part) and are better suited as extensions to other parts of core neovim (e.g. options for plugins might need better `vim.{o,g}` support for nested objects, unsure). Maybe specifying nested dependencies might make sense to add to `vim.pack`.
All this to say: yea, now it is more verbose, but it doesn't have to be.
If a "developer" can't manage to read one paragraph in a readme, maybe the "developer tool" is not for them. As much as I usually hate gatekeeping, basic reading comprehension is a skill I'd happily gatekeep at.
Gatekeeping is much maligned (and not without reason), but I think that the results of no gatekeeping have proven far worse than the gatekeeping ever was. Sometimes, if someone can't put the effort into something, they should be shut out.
There's nothing AA could "fix" here, this depends entirely on volunteers uploading the books. Your best way to help is to buy the books yourself, use a book scanning service (eg. 1dollarscan), and upload it to ZLib/LibGen.
You can also make a book request on ZLib, that way someone else will be able to do that for you if they want to
That's not Arxiv's role. Arxiv does not manage any review process. It merely hosts preprints. The reviews will happen if you submit to an actual journal or conference, which is entirely independent of the arxiv submission.
