I agree -- and going one step further, WITHIN higher education, there seems to be somewhat of a stigma against training for real-world, hands-on, applications. I was pretty lucky to attend a college that encouraged students to work on projects that could become viable products... but from what I hear from friends, it was the exception.
Just to provide another data point from my own college experience, I actually ended up dropping out from my school because I got fed up with the fact that their program focused too much on application.
This is a school whose computer science curriculum circa 2004 still included COBOL because one of the major employers in my area is the banking industry. (Coincidentally, the CS building carries the name of one of the big names in that field here).
CS is a field where the theory end of things are often the most important thing you could take away long term, so having that kind of focus on tools in general (let alone ones that are hopeless obsolete for most purposes) is just insane.
Like everything else in life, it's all about balance. That said, I can't blame academia too much for erring on the side of theory.
I agree with what you're saying -- I thoroughly enjoyed the pure theory classes as part of the CS curriculum. I also agree that it is more important to teach concepts than specific technologies. That said, I think there are schools that fail to teach concepts as well... things like working as part of a team, using source control and designing a product modularly and writing code which would be considered "production quality." There's a tendency to put those things off because it is "just for a school project."
