Spot-on about java.
Regarding Slashdot, I think that Slashdot just reflects the state of affairs in software development (or the world) in general. Younger generations appear clueless, since they don't know certain obvious things. They will therefore reinvent a lot of wheels, and while doing that, inventing a few new things, some other things just like before but a bit different, while all the time making some old stuff irrelevant.
It is to expect, but It might get worse. I'm a bit worried that a lot of young people don't seem to be able to read, as in "read a lot of text, fast". One indication is that a lot of new projects have video introductions and video tutorials instead of text documents.
I mean, why watch a 40 minute long video to figure out if a toolkit might be of use or not, instead of skimming through a few documents for 2 minutes.
But then, It's clearly is a huge effort for many to read a long document - maybe they can't skim or speed read and they need to subvocalize but a lot people don't like to read long texts.
If it's "quicker" to watch a video then less is learned since it's not as efficient as speed reading. Maybe the youtube generation have learned to skim through videos quickly but I doubt it.
Also, the universities are not exactly excelling at producing good developers ( the trade , not researchers ) . Further, very little seems to be focused on "modern history" other than unproductive academical anecdotes. I think that schools should stay away from teaching "products" but maybe there is value in exploring historic and existing products and ideas. There are some giant's shoulders to stand on, or at least code monkey shoulders, actually, but it's hard to know since some of the knowledge is stored in long boring texts, and most just exists in wetware outside academia.
I mean, no one would have been using PHP (or creating PHP) if they had paid a minimum of attention to what's been happening the last 30 years.