It's hard enough to find reviewers in the same field. I imagine finding statisticians to review papers from fields they don't care about would be problematic. You probably know that reviewers work for free.
The big difference between RapidJson and sajson is surprising to me. When I benchmarked them their performance was comparable: https://github.com/project-gemmi/benchmarking-json . Did you use RapidJson in full-precision mode?
By the way, nativejson-benchmark (from RapidJson) has a nice conformance checker that tries various corner cases. But you probably know it.
I bought a £500 e-bike from a supermarket 3 years ago and I've been using it for daily commute since then. I have 9km to office, e-bike is a practical option. Cheaper models, like mine, have motor either in front or in rear hub. Both work fine, you don't really need a $2000 model with a crank drive. TFA claims that crank drive improves the bike's center of gravity :-). Actually it's more about being able to change gears between the motor and the wheel, but hub motors are also fine, at least up to the legal speed limit in Europe. The models sold in the E.U. are limited to 25km/h (15mi/h), I think in Japan the limit is even lower.
OK, it was a selective quote and there was no refusal. Ubuntu developers just want to fix first all the bugs that matter for Ubuntu users (which is as distant now as 5 years ago, in practice it's the same as refusal).
So there is a contrast. Ubuntu devs haven't made what would be a nice gesture toward their upstream distro. OTOH SUSE provides resources for building packages for several unrelated distros.
I use OBS to provide Linux packages of the latest version of my project for multiple Linux distros. Because of the release cycle Linux distros usually come with older versions of the program, so when the user reports a problem it's handy to have an easy way for her to update and try the latest version. (Compilation from sources is not an easy way)
I spent many hours to write a spec file portable enough to build on OpenSuse/Fedora/RHEL/Mandriva (there was Mandriva Linux at that time), and to prepare debian/ directory, but after this initial work updating spec/debian and triggering builds for a new release takes only a few minutes.
I really appreciate that SUSE is providing resources to build packages for other distros. This is in contrast with Canonical refusing to build packages for Debian in PPA[1]:
"PPA builds consume a great deal of resources and it's difficult justify spending that amount of money as a gift, especially if the net effect would be to encourage people to build packages which don't necessarily work with Ubuntu."
I've been using devtoolset (one of RedHat's SCLs, I think the first one) for almost two years. It provides the latest GCC and other tools for developers. Using it on RHEL 5 gives well optimized and portable binaries (glibc is backward compatible).
It's fantastic that RedHat provides RPMs with the latest tools for older systems.
Regarding the scl tool itself from user's perspective, it's a step back from Environment Modules that has been around for 20+ years. Some admins even replace the scl command (which just sets a couple of env. variables) with modules.