You’re highlighting how subjective things can be and I don’t disagree.
What isn’t subjective is the generations of the 1900s are the first to leave behind an existential threat driven by wasteful economic choices and they seem to be indifferent to doing so just to have fun.
Myself and lot of other software engineers I have worked with feel our jobs are meaningless; the future won’t care about these technologies. They’re hardly regenerative medicine or something so life changing daily life itself is improved forever like indoor plumbing and electricity.
But we feel captured by nostalgia for this work and form of economics, and apathy for a whole lot of people who will be dead before climate change is real problem
Most people aren't solving deep societal needs in their free time. If you want to limit it to software, most of us have jobs that hardly improve society or the planet. Most open source code isn't advancing society. What I don't understand is why you've singled out the participants of this particular project for your ire.
I don't know any of the individuals involved personally. My guess is they're not the ones that built physical products with PFCs, ran coal-powered factories and operated strip mining operations, designed nuclear weaponry, or even fly personal jets. I'd hazard to say your average front-end developer chugging through batteries with inefficient frameworks is doing more harm than this project.
If your aim is to clean up the tech industry, I think that's laudable. I believe tech people have for the most part shirked their own contribution to our carbon footprint or other societal needs. But, I think you'll find there are much bigger targets actively doing harm (or certainly not helping things) regularly because it's profitable and/or convenient.
In contrast, many of us treat computers as a magic black box. The abstraction is great for productively building web apps. But, we've lost sight of how things work and I think that's led to steep decline in performance and, perhaps, security. I don't pine for manual resource management in all things, but knowing how syscalls work can help build context on when and why you should use them. Revisiting how to build an OS that isn't rooted in decades-old Linux or BSD code could be really instructive.