Yes, if they know how to run a debugger on an executable that is compiled without debugging symbols and can figure out how to get the data out of that symbol

There's nothing to figure out. The first thing the executable does is to load the entire original program into a variable.

Source code is also obfuscated using a simple key to avoid extracting the string from the executable.

The original program is provided intact in that variable unless bleach is used. Intact is not obfuscated.

Ignoring the practicality of hiding the code in most situations just because someone can get the code is like deciding to not lock your house anymore, just because locks can be picked.

I didn't say you shouldn't; I said you didn't.

Yes. Someone can get in. That doesn't mean there is no reason to try to make it difficult.

You couldn't have made it easier if you tried.

I'm glad that you are (possibly) clever enough to get the data out of a perlc obfuscated program. Most people are not.

On the other hand, it's trivial with daveola's perlc.

Again, if you don't want to use an obfuscator than don't. Many people find them useful. You may find them foolish.

I'll repeat: I didn't state my thoughts on the use of an obfuscator; I simply pointed out that daveola's sucks. It simply doesn't do what it claims to do.