Description
"What?! A conference about goto in 2026?!
Come on, we all know it's evil and should never be used!"
Really? Never? Everyone? Are you sure?
How would you explain this to a junior developer?
In a factual, objective way, with arguments, without falling into dogma or "it's ugly".
What if I told you there are cases where using goto is relevant?
And even cases where it's preferable to alternatives?
Situations where maintainers of major projects use it consciously?
In this talk, we'll use the seemingly simple example of goto as a lens to explore the importance of critical/analytical mind.
Let's use it to form our own informed opinions!
