I don't really think this is a particularly childish exchange. But either way, it struck me that when you consider the reason for the exchange: a unilateral decision made by Google -- that kind of reminds me of how Google handles support: they don't.
On another note - does chrome/chromium build on freebsd? Is there an equivalent api there?
I certainly sympathize with the chrome/chormium team: they're of course free to abandon users on old kernels/os'. It is a bit odd to demand a new kernel (newer than most Android installs uses) for a browser. We've come to learn to live with not having stable and secure browsers (choose either - usually choosing the updated, secure browser makes more sense). It's a bit more hairy when you need a new kernel. But I suppose newer hardware can just run Chrome (or chrome os) in a kvm vm anyway...
On another note - does chrome/chromium build on freebsd? Is there an equivalent api there?
I certainly sympathize with the chrome/chormium team: they're of course free to abandon users on old kernels/os'. It is a bit odd to demand a new kernel (newer than most Android installs uses) for a browser. We've come to learn to live with not having stable and secure browsers (choose either - usually choosing the updated, secure browser makes more sense). It's a bit more hairy when you need a new kernel. But I suppose newer hardware can just run Chrome (or chrome os) in a kvm vm anyway...