Your theory falls flat when you hit point #2
The following packages do not exist.
google.io.*
google.threads.*
google.db.*
google.util.*
If, in the future, google does add those libraries, I would fully expect them to be opensourced.
I can see how you misunderstood the posting. Please, let me help you.
I will do this in two parts:
[PART-1]
I am sure that you only missed the that I used "e.g." (what is an e.g.?) in the above, otherwise you would not have made the mistake of thinking that it could have been referring to anything else other than an example being posited for the discussion.
Those names were examples... hypothetical, if you will.
Now that that is all cleared up, give the post a re-read... but only after reading PART-2 which comes next...
[PART-2]
Also consider another good point:
Why block the ALREADY open source standardized community developed and supported implementations only to provide your own replacements? Even if as you suggest that you "would fully expect them to be opensourced", WHY NOT support the existing open source community? WHY NOT support the existing open source solutions?
"Look! There! Evil!.. pure and simple, total evil from the Eighth Dimension!" -- Buckaroo Banzai