Cutlass, I could write a longer post (and probably will on request), but Nick Rowe has addressed the whole "technology and jobs" question
here in a somewhat better way than I probably could.
--
More directly, the article makes a lot of good points. He sort of discounts the "creative" half of creative-destruction, in the sense that while some industries fade in the face of technological change, other industries grow. We don't have a thriving buggy-whip industry anymore, but at the same time employment in the IT sector was 0 back in 1850. Technology cuts both ways.
"Do we really need jobs"? Yes, to generate income. But we don't necessarily need 40-hour-per-week jobs. The workweek adjusts so that unemployment stays low; wages also do some lifting in the adjustment process. We don't have a 60-hour workweek and there's no reason to think we'll stick at a 40-hour workweek. "Mass unemployment in the face of technical change" ignores the fact that hours and wages adjust to keep a high-employment equilibrium. Proof: the past 80-some years, in which there's been a lot of progress but no corresponding rise in trend unemployment.
--
The high unemployment we see right now is recession-related, not technology-related.
If it were tech-related, and automation were pushing people out of jobs, then why wasn't unemployment at 9% back in 2005? Were there such massive changes in technology between then and now? Of course not.
...more to come if any of this is remotely interesting. Lots of it is a rehash of stuff one would learn in intermediate macro. See Nick's post linked above.