Those are very different things. The whole point behind loot boxes is that you never know what you're going to get, and it might be quite rare/valuable. With both Blue Apron like boxes and airplane tickets you know and select exactly what you're going to get.
I've been using Firefox as my daily browser at work, home, and on my mobile devices, and I've literally never had issues with Firefox taking up too much RAM. Chrome on the other hand was always one of the main culprits when my computer(s) would start to slow down.
This is the problem with anecdotal evidence; everybody's subjective experiences are slightly different and further colored with their own biases, so you can never get hard facts out of it.
> You can't push to origin unless it's your own project or your team's. We're talking about PR-based workflows.
Having to create a fork per PR is a rather antiquated way of doing it. In my experience, you can almost always push to origin and create a new PR from the branch, but maybe I've just been lucky with the projects I contribute to.
> It's not a constant cost, unless you're saying you only ever intend to contribute to one project ever. It's a fixed cost that you will pay N times, where N is the number of projects you contribute to.
It's a constant cost in the same way that looking up where to submit your patch to is a constant cost. You will pay both N times, where N is the number of projects you contribute to.
> Please actually point out how the GitHub workflow can be even more simplified than what I outlined above
Adding a remote is generally a one-time cost and is unneeded for every PR, so adding that command (along with all the associated comments) makes it appear more complicated. The reality for most GitHub users is that they simply have to do: