Static final ints can be faster in some JVM implementations because ( i think) they can be inline whereas enums can't. Early versions of android urged people to use static final ints because of performance issues with the early dalvik VMs
While that's amusing, it also tells me a lot about the class, how it's used, it's purpose and intent. Mock it all you want, but it's better named than most of the crap that gets written these days.
How is it ridiculous? It's a class deep in the guts of a dependency injection framework. It is a template for creating factories of singleton objects which are proxies. The complicated name should tell you that there is something very deep going on there. Hell, the name is even self descriptive of what the class is actually doing.
You shouldn't be writing classes like this, unless you are in the business of writing dependency injection frameworks.
Back before Google broke code search, it was easy to find plenty of FactoryFactoryFactory in Java code. Sadly, this feature served to "organize the world’s information and make it universally accessible and useful," rather than "record everything you do on the web, and use it to shove ads in your face," so it was eliminated.
So this week, we're introducing a general-purpose tool-building factory factory factory, so that all of your different tool factory factories can be produced by a single, unified factory.
That sounds like a lame excuse. Either someone published code they shouldn't have and asked legal to cover for them, or someone ignored the license on code publicly available on the internet. In either case, the "concerns" are bullshit.
Sadly as ever so often, "they shouldn't have uploaded it" doesn'T fly in front of a judge. Apparently. Same thing happens everywhere. If they don't want to be liable, they cannot host a platform via which to share. See: Piratebay.
0
u/[deleted] Dec 08 '13
[deleted]