In fact, what you learn now in the CS program (except for higher level concepts) may not apply 10 years from now.
CS fundamentals have been around (officially) since the 60s and haven't changed much. (See Donald Knuth.) Unless there is some redefinition of rudimentary math and/or binary interpretation, not much will change. C and C++ have been around for a long time. Linux is a variation of Unix: same thing. (Linux first officially surfaced over 14 years ago.) Other than differences in 'flavor' CS hasn't changed as much as the Microsoft world would like for us to believe. And Donald Knuth has written a series of books, about 50 years old :!:, that are still regarded as the 'bibles' of CS. So, I guess I really disagree with this statement.
It's true that Python, Perl, Java .NET (C#), whatever are 'newer', but are just implementations getting to the root of solving classic CS problems. It doesn't matter, as much, about the languages (that do change) as understanding what they're trying to accomplish. CIS will not and will probably never delve that deep.
I agree, in a corporate environment, it will ultimately depend on the technical aptitude of the person, not the degree. But to architect a new solution in a networked environment today ultimately requires CS, not some technical management degree. If the goal is to manage, then a CS degree will still help, but CIS would be better. Working for a large company, our group respects CS a lot more than CIS. The directors here have CS concentrations, not CIS.
Just thought I'd chime in...it's Monday, after all. :mrgreen:
E.