@PauloCereda The question there would be: 'What's the advantage?', and I'm afraid ATM I don't see one for an open project (very different if one is doing commercial work and self hosting)
@PauloCereda They have deep pockets ... any hosting in the end needs money, and that means either venture capital or a rich backer, at least until some business model is established
@samcarter Er, yes, but the usual rule is that unless a function is documented by a dependent package/class (unlikely), one should always load the package that explicitly provides a command
@JosephWright but this risks to sent user into option clashes. If they see things like \usepackage{xcolor} in their code, they might be tempted to add an option and then you'll get the 1 million duplicate of the "how to avoid option clash" question
@samcarter It's about the 'guarantee' of stability: as a package author, I might change what I use 'behind the scenes', and user documents should still work. Classes are I agree more complex.
@JosephWright However as author I should also feel responsible for backwards compatibility, I'd count removing a previously loaded package to that. So this would at least needs documentation.
@samcarter So, would it make sense that I still place \usepackage{etoolbox} in my example code and comment it out and add as a comment that it already has been loaded by beamer?
@JasperHabicht Personally I would not do that. I don't think the negligible risk that at one point etoolbox might be removed from beamer justifies additional noise in the code. I'm sure @JosephWright will disagree :)
@samcarter Well, considering that there are packages that redefine certain macros (which then, for example, take more arguments), I can see a certain sense behind this rule. in this very case, however, my example would only work with beamer anyways. so I just leave the code as it is now.
Since yesterday something's off with the SE webpage for me (chromium on openSUSE Leap 15.1). I cannot write or access comments, and when writing an answer I see no preview, nor the whole buttons, nor I can insert pctures. Is someone experiencing something similar?
For years I've been browsing the site using the SeaMonkey Gecko-engine-based browser. It has the following user agent:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.10
Suddenly this afternoon, interacting with most of the site of the site seems broken:
...