Anecdote is not the singular of data and all that, but at the major game development studio I work at, no-one at my team has even /heard/ of git, and when I try to explain what a distributed version control system is I get blank stares.
Do they use perforce? It seems to be rather popular in the game industry, in part because its model suits projects that have a lot of large binaries in their repository.
Of course -- everyone in games seems to use Perforce. There are no better alternatives, including p4-git, and believe me, I've looked. Subversion is passable but slow.
Even though I use git for all my personal stuff, if I started a console or PC studio, I too would be setting up a P4 server the first week rather than even experimenting with git.
As you say, it seems to be the only code-oriented VCS that also comfortably handles large files (especially larger than available memory) with reasonable speed.
Traditional version control systems consider giant files a user smell.
Many (read: almost all, I'm willing to bet) web developers will be completely ignorant of trends in embedded programming. Many (read: almost all, I'm willing to bet) embedded programmers will be ignorant of trends in web programming. It is unsurprising that many programmers who do the overwhelming majority of their work in the closed-source arena would be unaware of trends in the open-source community.