IMO: Paranoid about the implications, slightly less worried about it applying in practice. As shown by the DRM schemes used in modern games, this type of obfus

IMO: Paranoid about the implications, slightly less worried about it applying in practice. As shown by the DRM schemes used in modern games, this type of obfuscation comes at the cost of performance: Unless you want to compute a sensitive function at the user's end in an obfuscated manner, it'd be much simpler to just run that function on your end and optimize it in terms of running costs & performance. Such a design would also runs counter to the everything-as-a-service model that companies are trending towards, as it places more power back at the user's end, even if the user can't decipher the obfuscated function's inner mechanisms. Such a design would reduce the need to phone home, and thus the need for EaaS.