I'm sorry, but I am really baffled by what I'm reading.
> Like I ranted recently here in HN, can we stop with the millionth LISP interpreter already?
Except, the millionth LISP interpreter is a hobby project, that people are making on their own time, not during work? I get it's annoying to see something you've seen before, but you know, you can ignore it.
Play is an important part in learning. The millionth LISP interpreter, game engine, whatever is fine. From my experience, the people building these things gain a lot more valuable experience than just doing college or even just having a prior job.
> We have people dying in hospitals because the software of the heart monitor glitched or misread a sensor. Can we get on those problems instead?
Do you have any idea how current problems actually get decided for in industry (not only software, but in general)? It's not "this problem gets tackled because it's cool", it's because of money. Do you think bright software engineers love working on Microsoft Word or better AdSense because they think it's fun?
Also, this sounds really stupid to say, but this seems to be what you're implying when you say "keep play out of work": do you really think the same people working on embedded systems for heart monitors are the ones writing LISP interpreters...somehow...at work?
There's also something that plagues HN and it's that they think the software industry is somehow uniform. Medical devices get regulated under the medical devices industry, commercial airplanes get regulated under the aviation industry. The pure software industry is not the only place that hires software engineers.