I actually like this. I think we should consider the logging industry a failure unless we have a tree that is cut down by a female logger, that is then processed into a 2x4 by a female saw mill worker. Then maybe take it that one step further into having it placed into a house by a female carpenter.
This game is fun! (serious sarcasm).

And Java can be concurrent as well. It depends on the framework you are using to run it. Tomcat is thread bound, but things like akka and vert.x are not. In fact I suggest you look at the vert.x site to examine the speed increases you get on multi-core java with vert.x vs. node.js. Plus vert.x is a polyglot so you can also do Scala if it makes more sense. It is all about using asynchronous programming techniques which you HAVE to do in JavaScript, since it is single threaded, and you can do with Java. node.js is more about using cheaper web developers to put together a back end that barely functions. The node.js code I have seen is so unmaintainable with massive promise structures that will make your head hurt. If you truly need to scale to those kinds of levels you can do it even better with Java and the correct runtime environment.

Funny you say they are not being utilized. Last weekend the bands were jammed end to end for the world wide DX contest. On the major bands the waterfall was full end to end. I made hundreds of contacts. Earlier I did a summits on the air activation and made over 30 contacts in an hour. Never mind the digital modes. The ham bands are alive and well, Jim Olsen K7JEO

Another funny story along that line. I bought my cabin from a former school principal and administrator. When I moved into it, I found a note on the sink reading: "Leek in Fawsett". I at first looked for a vegetable in there, but did not find one. It was deplorable to me that someone in the school system long enough to retire could not even spell these very common words correctly. Then I saw all of his 'fixes' around (split a pipe in two since it didn't fit easily, and tried hose clamping it), and felt very sad for the generation he mentored.....

Whatever happened to teaching the kids the fundamentals of math and logic, never mind reading comprehension? Guess what? All of that is far more important to learning to code than the actual code itself. I find it ironic to imply that the kids are lost if they don't start to learn actual code that young. When I started programming, computers weren't even really available to anyone. I had good knowledge of math and logic, and was able to figure it out on my own over 35 years ago, and keep up with 'all of the latest trends' and have quite a successful career.
What I learned that help me do this, was how to learn. Start teaching that, and you will find they are prepared for whatever comes down the line in the future. Stop making automatons.....
Jim

Yes, age discrimination is horrible and very real. I just hit 45 and am seeing it first hand. I work for a 'hot' type company and they actually said in a company wide meeting 'look around you. Notice that you don't see much grey hair. That is on purpose as we want people on their way up, not out'. I was shocked. Meanwhile their people 'on the way up' hack out some of the worst code I have ever seen. We could use a few more people on their way out to actually make some scalable and well architected products so our servers don't fail under the weight of this pile of crap they created. Thing that sucks is I am right now the best I have ever been with all of this experience and I am afraid it is going to get harder and harder to get a decent job.

Agreed to some extent, but how they are actually implemented in languages and what they mean kind of are... You just don't know how tired I am of working with people who can not understand the difference of pass by pointer, value, and reference though. Never mind a slew of other basics that really are important to understanding what you are writing is actually doing. The state of code is rapidly going down hill....

Or how about learn about the fundamentals of computer science. Actually learn what pointers are, pass by reference, multi-threading, type safety, and all of the things that implies. Then express those in whatever language you want. If you truly understand how computers and languages work, and what an enterprise system is composed of, you will likely have future proofed your career. If your language doesn't support many of those ( I am looking at you, JavaScript), then perhaps consider how much those jobs are likely to pay in the long run....

I like to use something that is in my head and I always have with me. That way it works when I scp, ssh, or whatever. Many times, I am not on a browser or necessarily even connected to the net. But I've been around a bit too so I am probably not typical that way..... Never mind embedded devices.