You don't want to live in a society where an increasingly large percentage of the population have nothing to lose.
Regardless of whether it benefits our industry or socioeconomic status, it'd be incredibly shortsighted to just do all of that at the expense of the lower classes.
Also someday you might find yourself needing things like medicaid. I once met a former SE who was on disability because he lost his sight. Protecting those things for others also protects them for yourself.
I can think of one valuable use-case: parsing through JSON responses for APIs with poor fields/response documentation -- especially if you have to parse through a ton of information.
I agree. Its a coin flip. We don't know what the long term effects of COVID are, we don't know what the long term effects of the vaccine are. I'd argue that we know more about what COULD happen with the vaccine long term and I'd rather place my bets on that. The alternative is hiding away for 20+ years and not getting vaccinated or contracting COVID, obviously not feasible.
Well, how will that public policy and enforcement come about? We live in a democratic society, so the only way the government will enforce anything is if people demand it. And for people to demand it they need to be aware of the issue and what's causing it.
I think that's where the confusion lies. Are people suggesting someone to write their own auth from the ground up, or write auth in coordination with their stack's auth library of choice?
It appears to me the assumption these people / articles make is that nobody is using existing hardened production ready libraries, but hand writing everything from the ground up for their todo app.
Because otherwise their message falls flat on its face.
Regardless of whether it benefits our industry or socioeconomic status, it'd be incredibly shortsighted to just do all of that at the expense of the lower classes.