QUOTE(mrttao @ Sep 1 2012, 21:11)

I have been using this script in chrome's native implementation for a couple of weeks without a single issue. What is it in tampermonkey that this is meant to use that is not available in native implementation? (and maybe someone with far more skill and knowledge then me can help you with a native implementation of said function too)
Yes, my script have a (unoffical) native Chrome support. Don't say it loud or everybode get the glue ;-)
The reason for the tampermonkey:
1. my first Chrome version ignored the embedet images in my script, tampermonkey fixed the problem
2. I can set the start moment for my script with. i know i can do the same with javascript listener - reason for my gm solution later
3. auto update when i update the script
4. gm/tm check the correct page to run, with pure js : my script have to run and start on it's own. nice with a single script, bad with a bunch of scripts
5. special catch for included scripts
The reason against gm/tm
1. it's a sandbox, this will slow down the script
imho: there are - from my point of view - more pros for tampermonkey. This result in my little Tampermokey Advice. The results are the same in the most browsers and i like the userscript header part.
But for the good of all Chrome users i try my best and ignore some GM goodies
*point to the native chrome + include jquery problem*
The "right" GM solution was faster but don't work without tampermonkey in chrome.
(faster with a bunch of scripts.)
And yes, you can run my script directly in Chrome - but i say it all the time: i will fix problems with the native Chrome but i don't like it. This is what i call "no offical support" (offical support make me cry, inoffical support let my growl)
__
finally: I update the script on the next weekend. The item part don't work right. Next time i will fix the bug and add new wishes and don't start a war on two fronts. Germans - every time the same stupid ideas...