There are a lot of web-oriented programming jobs, yes, but you can still find a fair number of jobs for non-web positions if you use the right search terms.
For example, a quick look at indeed.com returned the following:
"java developer" - 10k+ hits
"cobol developer" - 200+ hits
"c++ developer" - 2,600+ hits
"game developer" - 800 hits
"c developer" - 3,000+ hits
"linux kernel developer" - 100+ hits
"c# developer" - 4,700+ hits
There are a lot of developer positions that are web-based, largely because there are more people who need/want a web presence. Being on the web these days is pretty much required for doing business. This means that companies that aren't otherwise tech-oriented (and therefore wouldn't be hiring platform developers) are hiring developers. This creates far higher demand than platform developers would ever see (in sheer numbers, at least). There's also the fact that the divide between "web" and "platform" is quickly closing, with many platforms adopting web technologies for part or all of their platform.
The question, then, becomes "what do you want to do?" As a developer, sticking to one or two languages is generally not a good idea over the long-term, but it can work in the short term (COBOL developers still enjoy a fair amount of demand, due to the slow rate at which financial institutions change, for example). Sticking staunchly to "platform" or "web" development is, in my opinion, about as short-sighted as only knowing one or two languages. As developers, our job is to solve problems and build applications that our users can use and enjoy. Whether it's a platform application or web application should be considered in the same manner as any other decision -- is this a feasible option, given our resources and the user requirements? Additionally, there's a lot of cross-over between web and platform in a large number of languages -- most notably Python, Ruby, and the .Net languages, making the choice about which route to go even less about technical matters.
