It's cool, but I guess I don't see the point because I'm not sure how big the intersection is between users that can use Chrome developer tools, and those who can't disable this [0].
Yah... it took me all of 30 seconds to get past. Those doing this without understanding what they're doing are likely following an online how-to, and this wouldn't be that hard to explain in one.
This sort of brings me back to the days where you would obfuscate your javascript or entire page by hexing it (or even AES in one of the scripts I've seen!) and writing a javascript interpreter. One of the more clever ones I've seen was just inserting a tonne of newlines so that the actual page contents was way below the view-source window fold. I felt mighty stupid when I fell for that one.
Anyone who knows better won't use this, as they know it offers no real protection. Anyone who thinks that can protect their site using this probably won't understand why it won't work, creating a false sense of security.
This sort of brings me back to the days where you would obfuscate your javascript or entire page by hexing it (or even AES in one of the scripts I've seen!) and writing a javascript interpreter. One of the more clever ones I've seen was just inserting a tonne of newlines so that the actual page contents was way below the view-source window fold. I felt mighty stupid when I fell for that one.
EDIT: tone =/= tonne