I have no problem using Erlang when I need it, but eventually concurrency is a problem that every language is going to have to deal with more effectively than it does now. The Actor pattern makes a lot of sense to me conceptually, and makes it trivial to parallelize systems. It's not like Erlang's the end all, be all of programming languages, but it is a forward looking one. I look forward to other languages catching up with it.
I'm pretty sure the people in the Matrix will be confused when every printer in the world starts printing out "I will not throw paper airplanes in class." ... Of course, then the agents will reset the system and everyone will just experience deja vu.
What do you mean by "everything is turning into software"?
Also, while I agree that there's effectively infinite demand for new software (I can't imagine a day where all software companies and open source projects stop writing code), it doesn't mean that there's infinite room for new software businessnes -- especially the ones that start with a few hackers in an apartment cranking out a webapp in 2-4 months.
What do you mean by "everything is turning into software"?
Can't answer directly for pg but I know my whole field (electrical engineering) has pretty much been converted to software. Musical instruments, medical diagnostics, anything that deals with information processing, which in this day and age, seems to be migrating to a software function.
Erlang was designed for building scalable, highly available distributed systems. If it's not good at building other things, e.g. first person shooters, that's not a meaningful disadvantage.