Yes, it is definitely annoying for content developers. But I think this is not a bug and is indeed a feature. (it occurs too with web-browsers, after all) Cache does have its reason to exist, as it saves bandwidth (both provider and client) and makes stuff load faster. It is not really a “difficult way” of adding an additional parameter to the end of the url: it makes sure that anyone who loads the script is also using the same version if they have loaded the script before.
One rule of thumb with web development is that you simply should never, ever force end users to refresh their cache manually to use the latest stuff: instead gracefully use parameters or hashing to denote change.
Having the “open and run script from url” refresh functionality refresh the developers (here after Content Creator or CC) cache would only lead situation where the script wouldn’t match for all users loading the script (or asset) up, and would lead to CC would have to (if they forget to add the parameter) would constantly having to remind end users to refresh their cache for latest content. This sort of having to put parameters at the end of the url is more of a good convention to keep users update, and update their own cache when its needed, and only for the file in question.
So In my opinion, instead of flushing the file cache allocation -constantly- when pressing the load file from url, I think we should focus on better ways to CCs to develop scripts “locally” before the scripts are placed into a host to run for Forexample:
This feature should be present for locally run scripts from file: as you are throwing the latest file at the script processor. But we should go further: after Load script from File, if there are changes done to that file, it will automatically reparse and rerun the script from the file. Once its ready from “production” it can be thrown to the host, and the urls setup.
This way, you have a much, much faster method of development, that does not require you to deal with constantly jumping back and forth with ftp clients to the host and pressing reload / flush cache.
The only issue with this is figuring out how to develop those on entities. Maybe a local “domain” within the client where you can work on entity scripts.