You forget the new computer scientists and the people just learning about arrays that find this place sufficiently interesting to read around it.
I'm not one of them, but not everyone is far enough into their CS career to have come across the numerous contributions he has made.
In fact, with the web-development world we're living in, I imagine it's pretty easy to go very far in {php, python, <insert language here that isn't often formally taught>}, and write a ton of code (or at least stitch a great number of libraries together), even ones that use semaphores or some other construct/algorithm he's helped develop, without ever having heard his name.
I would say: "If you don't know who Dijkstra is, you need to read more algorithm books", or "you need to study more history", or "you need to read more academic papers", or "you need to work on harder problems."
I'm not one of them, but not everyone is far enough into their CS career to have come across the numerous contributions he has made.
In fact, with the web-development world we're living in, I imagine it's pretty easy to go very far in {php, python, <insert language here that isn't often formally taught>}, and write a ton of code (or at least stitch a great number of libraries together), even ones that use semaphores or some other construct/algorithm he's helped develop, without ever having heard his name.
I would say: "If you don't know who Dijkstra is, you need to read more algorithm books", or "you need to study more history", or "you need to read more academic papers", or "you need to work on harder problems."