I'm not the OP, and fealty to a language isn't why I was picky. But the reality is many software developers have substantial savings from a combination of well above average wages and non-extravagant tastes, and career paths which aren't based upon tenure, so they can always say "and others are busy accumulating two years of savings they'll never need doing things they don't want to do, because it's the default..."
And unless your investments are self sustaining - ie they throw off enough earnings to support your lifestyle without going into the principal - it is still dumb to have fealty to a language as the only reason you aren’t working.
He talked about a “burn rate” so he obviously isn’t in that position.
I talked about the burn rate. Personally I doubt using a particular language I specialised in would be a dealbreaker if I wrote code for a living, but I find the mentality that one must in all cases spend 40+ hours a week working in jobs less well matched to ones skillset and interests out of fealty to not consuming any part of the principal of ones savings (irrespective of how large they are) or making any other lifestyle changes even more unfathomable.
I didn’t say in all cases. I understand wanting to take a break because of burnout [1], family obligations, to explore a hobby, pursue a passion, etc.
But because of a language preference?
I specialize in AWS consulting + app dev. It’s something I’ve been doing for a decade, I know it well and I even did a 4 year stint at AWS working in the consulting department (full time RSU earning blue badge employee). But I wouldn’t refuse on principle to get a job that required me to spend all day on GCP or Azure.
[1] I really don’t understand burn out though. In 30 years across 10 jobs, when the “shit I have to put up with” got to high I would just get another job instead if toiling away
I shot you an email.