People SAY that CS is this big thing - but is it the real computer SCIENCE part - or do they mean code monkeys? CS was always meant to be much more theoretical than practical. About solving really hard problems in operating systems, efficient new kinds of hardware resource management, compilers, programming languages - not just writing the next web app.
I think computing is undergoing just as big a change now as it did when the
If I had to predict, the more traditional need of CS degrees are going to shrink and shrink as advances no longer require the bit-twiddling madness of the early years of computing. Hardware will easily have advanced so-as even the most inefficient algorithms for daily tasks will be just fine. No special knowledge needed. The small blobs of very high-perf code that will be needed will be done by small, very skilled CS majors (drivers, OS's, database cores, distributed memory systems, etc), but the majority of code/apps will be simply scripted/assembled together on top of these high-perf, highly-accessible API's. We already see it with abstractions like PhoneGap, Unity, etc.
No matter how slick or how polished their lies be, NSA's lies are still LIES
Amen. Let's remember how many times they've been busted for COMPLETELY LYING in front of congressional panels, in quotes, and most of their other public statements. Even if everything they've said is 100% true, it could (and likely is) completely neglecting to bring up any un-mentioned ways in which they are spying on the average US citizen.
I have stopped believing the NSA, FBI, and Homeland security is at all telling the truth about what they are doing. We probably aren't even seeing 1/10th of what they're actually doing; and both Obama, Bush, and Hillary are all on board with expanding these programs and the agenda as a whole.
Why is robotics so ignored/boring/avoided, by even a tech community?
It's a hardware problem. Most people here are software people.
That's very unfortunate to hear. I know when I studied CS in the 90's, the foundation was always based on understanding the underlying hardware. My OS class focused on hardware interrupts, protected mode operation, cache and memory hierarchies. The whole basis for strategies and methods of making fast algorithms depends on knowing how the underlying hardware works.
How can you call yourself a computer scientist if you don't understand the different fundamental architectures you run on?
Often statistics are used as a drunken man uses lampposts -- for support rather than illumination.