Why not distribute scripts as .java files and have the user compile to .class?

It's incredibly easy to fix scripts that are 'broken,' or even massively improve the mediocre, already working scripts available with only one or two edits (correcting ids, changing certain cases).

 

The problem is that the scripts are currently distributed, at least locally, as .jar files with the source no where in sight. So, if anything is remotely wrong with the script, the entire script is now obsolete or must be babysat.

 

Development in the script department right now is very closed to the community. If you want more activity and a larger base, then this must be changed.

 

Sure, you may think leechers will steal your code and re-release it as their own, but that already is a problem. Adding transparency to the distribution process will allow for leechers who steal code to easily be exposed for who they are, and be dealt with accordingly.

 

By allowing the source to be available, people can contribute snippets and various fixes of their own to the script. People can give back to the community.

 

Of course, this wouldn't apply to paid scripts, which would just be distributed as already compiled .class files.

 

 

Edited October 30, 201312 yr by cynush

because it's the easiest way to distribute local scripts without getting 100's of replies asking what to do with the .java files, specially if scripts are packaged.