According to Martin at gHacks, the fact that Google doesn’t yet support an extension system within Chrome means that there are some pretty significant ifs and buts about what’s possible and what’s not with the addition of Greasemonkey. Script loading and a metadata issues are purported to be conflict prone.
As Martin writes, “Only scripts in c:\scripts are loaded and only if the user adds the parameter ‘–enable-greasemonkey’ by appending it to the program’s shortcut.” He goes on to explain that, “The scripts are not limited to a domain but will work on all domains which is usually handled by the @include metadata. The metadata part is ignored which could be problematic....”
The reason for Greasemonkey’s emergence in Chrome, however stifled, is because the software’s creator, Aaron Boodman, is a Google employee, as Google Operating System’s Alex Chitu describes.
If you’re looking to give the latest Greasemonkey-enhanced Chrome build, you can venture over to the Chromium BuildBot website. You’re able to download the most recent development, but keep in mind that stability is not guaranteed.