I don’t think it matters. Learning a stack because there are a lot of hot job postings for it will only keep you in framework hell. If you had to choose, choose

I don’t think it matters. Learning a stack because there are a lot of hot job postings for it will only keep you in framework hell. If you had to choose, choose the one with a community that you like and want to be around. I’m happy I stuck by Node’s side all these years, sure its not perfect but part of the journey is growing with a technology as it matures in the market. From my experience, mid-range developers with a few years of experience working in different stacks rarely make high quality contributions to the project. The only exception is if they’re gifted cs students first. The devs with for eg. 10+ years working with Perl Dancer projects have so much you can learn from. So my advice would be to pick one and commit to it for as long as you can. To the point where you both love and hate it. Get to a point where you can contribute to an well known open source project that is built in it’s domain.