![]() ![]() |
http://www.greasespot.net/2009/11/greasemonkey-... 36000 Scripts... Well, from the source code, it don't care if they are good scripts or bad ones.
Browsers are progressing rapidly, however. Instead of get/set value, one could use DOM Storage, and HTTP Access Control standards, for making cross-domain requests, are being standardized.GM_setValue and GM_getValue are linked to the script (via the namespace), while the DOM Storage is linked to the domain. (see there). Also, DOM storage can be easily cleared by the site, while GM Values are protected from that. All of Greasemonkey's security mechanisms are a pure hindrance to all these scripts. If it went away, they would benefit greatly.If it went away, there will be other hindrances. What Greasemonkey need, is new APIs that make the hindrance an advantage. |
![]() ![]() |
GIJoe wrote:I tend to agree from my perspective but it's going to take some time to catch the current upstream up to par with the code... I can only guess this was the reason why Johan wasn't chosen over Anthony by Aaron... que sera sera. *shrugs* :) |
![]() ![]() |
From my test:
892 scripts with 10 fans or more... GM API: GM_getValue =412/892 (46.18%) GM_setValue =409/892 (45.85%) GM_xmlhttpRequest =372/892 (41.70%) GM_addStyle =253/892 (28.36%) unsafeWindow =249/892 (27.91%) [No API] =236/892 (26.45%) (average size: 9189 bytes) GM_log =208/892 (23.31%) GM_registerMenuCommand=200/892 (22.42%) GM_openInTab = 90/892 (10.08%) GM_deleteValue = 40/892 ( 4.48%) GM_listValues = 15/892 ( 1.68%) GM_getResourceText = 8/892 ( 0.89%) GM_getResourceURL = 8/892 ( 0.89%) Others: eval =210/892 (23.54%) base64 image =195/892 (21.86%) text/css =170/892 (19.05%) XMLHttpRequest = 91/892 (10.20%) text/javascript = 89/892 ( 9.97%) console.log = 88/892 ( 9.86%) document.cookie = 76/892 ( 8.52%) jQuery = 64/892 ( 7.17%) canvas = 15/892 ( 1.68%) sessionStorage = 5/892 ( 0.56%) localStorage = 5/892 ( 0.56%) globalStorage = 4/892 ( 0.44%) Seems like with 36000 scripts, he take a lot of poor scripts without API. |
![]() ![]() |
GIJoe wrote:There is little mention of the time factor as well. Not all the API methods have been out as long as the earlier methods. Some have also changed relatively recently in an attempt to improve their existing usage. Also there are several dynamic scripts out there that yield different results depending on usage... using static uso scripts doesn't include the full picture but at least Anthony acknowledges that on his personal blog at some level. It is good to have multiple interpreted statistics around... Thanks for posting your criterion. :) |
![]() ![]() |
If i add jQuery in the GM API, the [No API] drop to 224/892 (25.11%) with an average size of 6847 bytes.
jQuery = 64/892 (7.17%) |
![]() ![]() |
Test with popular scripts...
143 scripts with 10 fans or more, at least 4 reviews with a rating of 4 or more, and last updated since 6 months. GM_getValue =91/143 (63.63%) GM_setValue =91/143 (63.63%) GM_xmlhttpRequest =82/143 (57.34%) unsafeWindow =63/143 (44.05%) GM_addStyle =51/143 (35.66%) GM_registerMenuCommand =48/143 (33.56%) GM_log =43/143 (30.06%) [No API] =27/143 (18.88%) (average size: 13804 bytes) GM_openInTab =19/143 (13.28%) GM_deleteValue =15/143 (10.48%) GM_listValues = 4/143 ( 2.79%) GM_getResourceURL = 4/143 ( 2.79%) GM_getResourceText = 2/143 ( 1.39%) base64 image =46/143 (32.16%) eval =40/143 (27.97%) text/css =37/143 (25.87%) text/javascript =22/143 (15.38%) console.log =22/143 (15.38%) document.cookie =20/143 (13.98%) XMLHttpRequest =17/143 (11.88%) jQuery =15/143 (10.48%) canvas = 7/143 ( 4.89%) localStorage = 3/143 ( 2.09%) sessionStorage = 2/143 ( 1.39%) globalStorage = 0/143 ( 0.00%) |



