9050c4e4ac
This project was originally LGPLv+-licensed to encourage its use in a community that is largely copyleft-phobic. After further reflection, that was a mistake, as adoption is not the important factor here---software freedom is. When submitting ease.js to the GNU project, it was asked if I would be willing to relicense it under the GPLv3+; I agreed happily, because there is no reason why we should provide proprietary software any sort of edge. Indeed, proprietary JavaScript is a huge problem since it is automatically downloaded on the user's PC generally without them even knowing, and is a current focus for the FSF. As such, to remain firm in our stance against proprietary JavaScript, relicensing made the most sense for GNU. This is likely to upset current users of ease.js. I am not sure of their number---I have only seen download counts periodically on npmjs.org---but I know there are at least a small number. These users are free to continue using the previous LGPL'd releases, but with the understanding that there will be no further maintenance (not even bug fixes). If possible, users should use the GPL-licensed versions and release their software as free software. Here comes GNU ease.js. |
||
|---|---|---|
| .. | ||
| README | ||
| common.js | ||
| perf-class-define-methods-keyword-private.js | ||
| perf-class-define-methods-keyword-protected.js | ||
| perf-class-define-methods-keyword-public.js | ||
| perf-class-define-methods.js | ||
| perf-class-define-named.js | ||
| perf-class-define-properties-keyword-private.js | ||
| perf-class-define-properties-keyword-protected.js | ||
| perf-class-define-properties-keyword-public.js | ||
| perf-class-define-properties.js | ||
| perf-class-define.js | ||
| perf-class-get-property.js | ||
| perf-class-inst-anon-empty.js | ||
| perf-class-inst-named-empty.js | ||
| perf-class-invoke-method.js | ||
| perf-class-require.js | ||
| perf-class-set-property.js | ||
README
This directory contains the performance tests. These tests contain basic routines that perform a single action and output the result in seconds, with a basic description of what has been done. The timing is done via the native Date object to ensure that it can be run both server and client-side. It is important that each test performs only a single operation to ensure that the prior operations have no consequences on the previous, at least when run server-side by invoking a separate executable for each.