Hi Yakov,
I think that — apart from it's scripting nature — introspection actually is
what makes JavaScript so great and easy to learn.
Therefore, I would challenge you to provide good reasons / benefits for...
1. why code that can be introspected is less reliable
2. why code that cannot be (easily) introspected is more secure
- JavaScript really is not a secure environment at all
- if you need secure operations, perform them at the server
3. seeing objects in JavaScript as persistent and compiled in nature as
Java equivalents
- again, JavaScript is a scripting language despite the ability to
implement deicated oo libraries
To put it differently, I am a strong proponent of transparency. I see no
point in obfuscation, especially not in an OpenSource JavaScript
environment.
If I do publish minified versions of my stuff, the only reason to do so is
to save on bandwidth, nothing else.
Eventually, hijacking code that previously was easily accessible and not
obfuscated in any way all the more calls for keeping these trails as
accessible as they were before making the changes.
Cheers, Tobias.
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
