I couldn't possibly disagree more.

The composition of programs through pipes remains a brilliant idea, and an extremely effective way to get a job done. I've lost track of the number of times I've heard a new programming tool described as "It's like Unix pipes for..."

C is still a remarkably popular programming language, and it has proven surprisingly hard to invent a new language that's better than C in every respect.

Many people could benefit from the ability to connect multiple programs in the shell to get a job done, even if they're not programmers.

It's hard for me to think of any computer scientists whose work remains as relevant today as the people in this video.

> The composition of programs through pipes remains a brilliant idea, and an extremely effective way to get a job done

Except pipes were already present in another operating systems at the time, http://cm.bell-labs.com/who/dmr/hist.html

> C is still a remarkably popular programming language, and it has proven surprisingly hard to invent a new language that's better than C in every respect.

In 70's already had a few system programming languages better than C in every respect, safety, modularization, thread support, low level programming, you name it.

C's widespread into the industry is a consequence of UNIX adoption by the industry.

I think it was shared for its historical interest. While the gist of unix presented here is the same as the unix we know today, obviously many things have changed since the 1980s.

Most of the big concepts underlying Unix described in the video still apply very well to Unix today.

Right. I don't think I've heard of makewords or 'p' to print out a file, although gnu obviously has its substitutes ;)