Anyway, I think your perception is basically accurate, at least in my limited experience. Google is the wrong place to go if you're interested in working on a startup on the side. Between the draconian "all your IP are belong to us", the intellectual demands of your day job, and the numerous opportunities to try out interesting side projects under the Google umbrella, the path of least resistance is usually just to do your side-projects as Google-owned 20% time.
It can be a good place to learn a whole bunch of technical, leadership, and product skills and then do a startup. Google's quite a bit more open internally than most big companies, so you're exposed to a lot more than you would be at another large corporation, and possibly even more than in a startup. There are specialists in performance, accessibility, internationalization, security, and all these other tricky corners that startups typically muddle through, and the quality of documentation on how to handle those is much better than you'll generally find on the web. You get daily experience with scaling, such that thinking about how to build scalable solutions becomes second-nature. You're often directly involved in product decisions, and can see how your choice fare in the real world. You have a wide variety of hard UX data at your fingertips; much of this is cutting edge applied psychology, and isn't available anywhere else.
I think we're starting to see a trickle of Xooglers leaving the mothership and founding their own things. I know at least 6 of them personally, plus there're posts like this blog entry. In general, I think this is a very good thing for the Valley startup ecosystem, just like how Fairchild spawned almost all of Silicon Valley in the 60s, and Xerox PARC spawned much of the rest of the modern computer industry in the 70s.
It's kinda ironic that Google is totally open for users, but is a walled garden for employees. Meanwhile, Facebook is a walled garden for users, but is relatively open about letting employees publish and open-source infrastructure. (Actually, that's perhaps an unfair comparison: Google is also really open about letting employees open-source infrastructure, the problem is that Google culture tends to result in re-use of core proprietary infrastructure, such that when it comes time to open-source the software, it's impossible to disentangle from the parts that definitely can't be open-sourced.) Meanwhile, Microsoft is now relatively open for both employees and users, but is a walled-garden for developers.