I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I think you have to ask yourself what you're trying to achieve. Why do you want people to not be able to read your source code?
Obfuscation is "safe" in that it very rarely screws up, changes the meaning of some clever bit of code, and causes your app to crash. It's "safe" in that you don't run it in development environments where you can still step through it with a debugger even if the problem is only appearing in production.
I think you have to ask yourself what you're trying to achieve. Why do you want people to not be able to read your source code?
Obfuscation is "safe" in that it very rarely screws up, changes the meaning of some clever bit of code, and causes your app to crash. It's "safe" in that you don't run it in development environments where you can still step through it with a debugger even if the problem is only appearing in production.
Hi @moopet ,
I edited the post a little. Let me know if it makes sense now.