You need to first define what your goal is. Do you want to become a full-time front-end developer? Do you want to be a full-stack, etc. Different aspects will require a different subset.
First and foremost, you will need to figure out how to get more free-time so that you can master a whole slew of technologies that have come and gone in the last 20 years. This is a cold, hard fact. You have a lot of ground to make up for, and if you can't even start up a web site, it's going to be tough getting legitimacy as a modern front-end developer.
We use a combination of C++ and Java with an Oracle PL/SQL back end.
I've only been programming for just over three years though, so I'm still kind of in my junior stage.
I've started tinkering around with NodeJS but I'd hate for it to get lambasted just as soon as I've mastered it. The frameworks and tools in web development feel transient to me, and I'd hate to build my career on a foundation made of sand.
Sorry for the late reply.
I definitely feel like the longer I remain with my current employer the more I'll stagnate and the less employable I'll be over time.
We have plans here to start offering some of our applications through web services/web applications but realistically we won't even hit the implementation stage for another three or four years. SO as of now, most of the developers here basically only have raw desktop development experience.
I should say though that these positions I have interviewed/am interviewing for are back-end Java/C++ positions with companies that offer their products and services through web and mobile applications and not purely web developer posititions, so I would still be working mostly with either Java or C++ technologies and frameworks, just with an eye towards web and mobile delivery.
I don't particularly want to be purely a 'web developer' anyway, but i do want to learn more about web technologies, and I want to learn it as soon as possible.
It also doesn't help that I'm trying to (slowly) learn to the Android 6 SDK at home with an intention to try to pick up the Rust language as well. I'm clearly trying to take too much on.
Easier said than done, but I'd advise to just stick with the web dev right now and focus on the other stuff later (if ever). Web apps are increasingly standing in for native mobile apps (that's partly why I gave up on Android) and Rust hasn't really reached a level where it's lucrative for professionals. Just be pragmatic and catch up on your web stuff right now (like I am right now) and once you think you've covered your bases then you can focus on the "for fun" stuff (Rust - although it would be awesome if someone could prove me wrong).
So much XML, it feels like you need to write two or three times as much code to implement any functionality than you do on any other language/platform. It feels so heavyweight.
I think you're right though, I might delay picking up Rust for a while and learn some web tech. It was just going to be something fun to do in my spare time.