One other option is to switch to www-client/google-chrome...it's a bin package, so no compiling and I don't think it get's updated as often. I use that on my netbook, because compile times are atrocious. It works very well.

As far as regular chromium goes...I like the latest and greatest always....so I hope they keep them coming. Of course, I have a new machine that knocks it out in < 40 minutes.

Both google-chrome and chromium get updated nearly every time there's a bump upstream... else how would you get all those security patches? Credit to the devs for keeping up. But yeah, recompiling chromium is a bit of a pain.

A bonus from using google-chrome instead of chromium is that you'll get the built-in PepperF API flash, which is more up to date and secure than the netscape plugin flash. If you're only using chrome, you can then unmerge www-plugins/adobe-flash altogether. If you want to keep it around for another browser, you can still make sure it's disabled for google-chrome by going to chrome://plugins and disabling the NSAPI flash.

eh if you watch lots of videos, they get laggy with pepper flash on fullscreen that adobe flash doesnt do for me_________________A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it.