Bong Cosca

Given that F3 is the framework you rely on, it should be the app that should adapt - not the other way around. Would jQuery give up the $ because...

I will leave it to whatever the consensus is.

No go until v4 comes around due to backward compatibility. I suggest we open up a different branch for this as a bridge version.

Why not a configurable hive variable (like PASSTHRU) so we can maintain backward comptibility and at the same time allow the dev to make that decision to override default behavior?

As an example, the labels displayed in Gnome settings are: * Digital Output (S/PDIF) - Built-in Audio * Headphones - Built-in Audio * Analog Output - Built-in Audio * Headphone...

No objections here

Hashed keys are necessary to prevent multiple applications sharing a common F3 folder from overwriting conflicting keys.

F3 uses whatever cache backend is available or specified. Guess what happens when the cache backend is redis, memcache, wincache, xcache or PHP's apc/apcu and we use only plain identifiers?...

I just love this hair-splitting exercise, and I am elated that the community is still looking for ways to make this speedy framework faster - things that I never got...

Please provide stats to support the claim that rewriting the code will be **more** efficient that way. Benchmarks would be useful.