> in your js anyway. I do think it's a neat way to kinda hide your code so > some script kid doesn't steal your neat idea and put it on his/her > website. But that's about it.
All told, I'm not worried about script kiddies taking my code and making it work on thier site. I'm not competing with them. Nobody's going to hire them instead of me to do javascript. It's the people who are just as good or better than me who I'm worried about, and they're good enough to defeat the obfuscation relatively easily. Hence, pointless. I don't care if the newbies use it and it's powerless against the people I do care about using it. If my idea was so nifty that I wanted to keep it for myself, I'd run it as a server side process. Once something's in the hands of a user, you have no control over what they do to it. It would be neat though to do an end run around all of this and modify an engine like mozilla or khtml to parse all of this out into source and dump it to a file instead of rednering. All the people writing these things are assuming that all browsers or hoping that most behave the same way, that the view source option will only yield the source as downloaded, not as processed before rendering. Changing that would be a swift kick in the nards for the obfuscators. 'the obfuscators' would be a decent band name though if it isn't being used already. tack _______________________________________________ Bits mailing list [EMAIL PROTECTED] http://www.sugoi.org/mailman/listinfo/bits
