As the discipline of Requirements Engineering approaches its 50th year, software pundits call (again) for its early retirement. Outside of research, RE’s future appears murky. Requirements jobs posted to LinkedIn are fewer in number, and fewer companies resource RE as a critical capability outside of those developing safety-critical systems. Fewer practitioners participate in RE events - possibly because fewer practitioners even exist. Rumors of RE’s irrelevance are greatly exaggerated, of course, as they have been each time a new shiny practice or tool attracts attention. From Agile to AI, the “RE killer” lurks just around the corner. Will the latest existential challenges to our discipline expose its fragility and limit its future? Or will Requirements Engineering prove itself not only durable but antifragile - a discipline and community that becomes more robust with adversity? Multidisciplinarity - its exclusion or its embrace - will determine its future.