You'd fully deserve that violin played for you later on in your career.
You might say most of my comment was just a bunch of assertions, but they were assertions about my own perception of my own experience. I think you have a higher burden to elaborate when you're making assertions about someone else's experience, especially when it contradicts what they allege.
* I have experienced what software development was like 25yrs ago, when it also took a lot longer to gain seniority and responsibility.
* I started my career in a different engineering field. I saw a very different age<->seniority progression than the quick one in software. In fact that was why I switched to tech even if software was slower back then than now.
The combination of both those was the basis for claiming that young software devs have been in an extraordinarily privileged position in recent years. Do you have any idea what it's like outside software?
You're going to have to make a better case that young software engineers these days experience ageism at a similar level to other professions or time periods. It is now an industry that skews young and quickly discards age. You'd also need to distinguish between lack of experience and just being young to claim it's ageism.
And the age groups you were deriding were the ones that broke down those barriers for younger devs in the first place. Did you consider they would've experienced worse and sought to change it?
Your non specific comment seemed like an extremely self centered view of the wider industry that lacked perspective and contradicted a near universally understood situation. You were the one making the extraordinary claim that needed backup.
Your incredibly broad generalisation got a necessarily broad reply which you're now complaining about just being an empty assertion. You did nothing to elaborate about your experience was - what did you expect? Maybe if you'd been more specific about what you've faced you would've got different answers.
Facing that again when at your most experienced and valuable makes a lot less sense.
(1) Be yourself (2) Provide value (3) Take on some of the boring stuff that adds to business continuity
Number 3 is not sexy, but good management notices.
You didn't really read that part through before posting, did you?