A few quick observations from a "seasoned" Curl beta user:
1. Reliability: Although it may be easier for an end user to have the browser bundle up required software instead of the user needing to download a plugin, one major advantage of a plugin technology IS reliability. As long as the software vendor controls the engine (i.e., the "compiler") itself, reliability is in the hands of the vendor, not the hands of diametrically opposed and relatively disinterested browser vendors.
2. There is a means for obscuring code. Application code can be processed such that the code is compressed and obscured, yet can still be interpreted by the plugin.
3. Curl seems to have identified integration as a key component in their quest for acceptance. Although there is supposed to be very little you couldn't do all in Curl, they've very heavily promoted interoperability with existing technologies.
Slashdot Mirror
A few quick observations from a "seasoned" Curl beta user:
1. Reliability: Although it may be easier for an end user to have the browser bundle up required software instead of the user needing to download a plugin, one major advantage of a plugin technology IS reliability. As long as the software vendor controls the engine (i.e., the "compiler") itself, reliability is in the hands of the vendor, not the hands of diametrically opposed and relatively disinterested browser vendors.
2. There is a means for obscuring code. Application code can be processed such that the code is compressed and obscured, yet can still be interpreted by the plugin.
3. Curl seems to have identified integration as a key component in their quest for acceptance. Although there is supposed to be very little you couldn't do all in Curl, they've very heavily promoted interoperability with existing technologies.