+1 because compressing and optimizing them with compilers like google's closure compiler is very expensive.
>> Hi, >> >> At the moment when a PackageResource is requested in production mode Wicket >> always re-reads the file from the disk, then executes any >> ITextResourceProcessor on it and finally delivers it. >> This is true for normal resources and for bundles. I just filled >> WICKET-5344 - bundles does all this twice per request. >> >> My question is: should Wicket do all this again and again for each request >> or we may add some caching which can be switched on/off with a new setting >> in IResourceSettings ? >> >> The benefits are: >> - reading from memory is faster than from disk >> - less CPU time (ITextResourceProcessor is run just once) >>
