Hi Jason, Thanks for the comments....
> > Where's the downside? > > For any of your ideas to work well, I think REBOL needs at least a standard > default tool + paradigm for propagating secure passwords and time-limited > keys. Something people can build upon. Some mechanism which can scale from > developer-to-developer all the way up to commercial shrink-wrapped REBOL > packages. I'd thought of that too. It needs to be built into the core so that "encapped" applications can run for (say) 30 days or 50 invocations or 100 files-converted or whatever, > A downside would be anything which hinders open development and sharing as > REBOL community does now. That's true. But the script library and this list would let us all still share snippets and insights. And the "professional" developers could post reduced-function versions of the "commercial" products as source code in the script libraries. That'd whet some people's appetites for the "real thing" while allowing access to their source code so we could see how good they are at Reboling. Sunanda. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
