5 ms·

This is why Grease Monkey existed. How many per-site plugins can someone have? http://www.greasespot.net/ http://www.greasespot.net/

by ssahoo 10y ago

unethical_ban 10y ago
To your question: A lot. How easy is it to install a chrome plugin vs. install a packaged, auto-updating Greasemonkey script? What is the real difference in performance?
- sjs382 10y ago
  Realistically? Not much. But I just installed it and while Chrome is running, it's taking up an additional 57.1MB of memory right now. That said, I've installed it and I think I'm going to keep using it.
  - mofle 10y ago
    A greasemonkey script in Chrome would take the same amount of memory or more, as Chrome just repackages it as an extension on install.
    - silverwind 10y ago
      I'm pretty sure that's not how Tampermonkey works.
- deleted 10y ago
  [deleted]
mofle 10y ago
This extension redirects requests before they've even started, making it much faster than what's possible with a Greasemonkey script. Greasemonkey scripts are also hard to discover and install these days.
- silverwind 10y ago
  Userscripts can also run before any content scripts through `@run-at document-start`. With a browser extension, you're giving up portability, security (an extension can wreck a lot more havoc than a site-specific script) and the freedom to publish without being dependant on a "store".
  - mofle 10y ago
    This extension redirects before a request is even made. `document-start` runs when the whole page is downloaded, but before the DOM is constructed, which is a lot slower. As for portability, both Firefox and Edge are committed to supporting Web Extensions, which is pretty much the Chrome extension API. This extension is not tied to any store. You can install it manually exactly as you would with a userscript. Actually, userscripts in Chrome, are just re-packaged as native extensions on install.
nikcub 10y ago
Here it is as a Greasemonkey script: https://gist.github.com/nikcub/b8cf72f564cde9000875be798e883928 https://gist.github.com/nikcub/b8cf72f564cde9000875be798e883... Most people don't know this but Chrome supports GM scripts natively - just save the file as `whatever.user.js` and drag + drop it onto the extensions window. One downside of this approach: it redirects to the mobile interface after the HTTP request and DOMReady

This is why Grease Monkey existed. How many per-site plugins can someone have? http://www.greasespot.net/ http://www.greasespot.net/

by ssahoo 10y ago

This is why Grease Monkey existed. How many per-site plugins can someone have? http://www.greasespot.net/ http://www.greasespot.net/

unethical_ban 10y ago

To your question: A lot. How easy is it to install a chrome plugin vs. install a packaged, auto-updating Greasemonkey script? What is the real difference in performance?

sjs382 10y ago
Realistically? Not much. But I just installed it and while Chrome is running, it's taking up an additional 57.1MB of memory right now. That said, I've installed it and I think I'm going to keep using it.
- mofle 10y ago
  A greasemonkey script in Chrome would take the same amount of memory or more, as Chrome just repackages it as an extension on install.
  - silverwind 10y ago
    I'm pretty sure that's not how Tampermonkey works.
deleted 10y ago
[deleted]

mofle 10y ago

This extension redirects requests before they've even started, making it much faster than what's possible with a Greasemonkey script. Greasemonkey scripts are also hard to discover and install these days.

silverwind 10y ago
Userscripts can also run before any content scripts through `@run-at document-start`. With a browser extension, you're giving up portability, security (an extension can wreck a lot more havoc than a site-specific script) and the freedom to publish without being dependant on a "store".
- mofle 10y ago
  This extension redirects before a request is even made. `document-start` runs when the whole page is downloaded, but before the DOM is constructed, which is a lot slower. As for portability, both Firefox and Edge are committed to supporting Web Extensions, which is pretty much the Chrome extension API. This extension is not tied to any store. You can install it manually exactly as you would with a userscript. Actually, userscripts in Chrome, are just re-packaged as native extensions on install.

nikcub 10y ago

Here it is as a Greasemonkey script: https://gist.github.com/nikcub/b8cf72f564cde9000875be798e883928 https://gist.github.com/nikcub/b8cf72f564cde9000875be798e883... Most people don't know this but Chrome supports GM scripts natively - just save the file as `whatever.user.js` and drag + drop it onto the extensions window. One downside of this approach: it redirects to the mobile interface after the HTTP request and DOMReady