Dean Wampler discusses the merits of several controversial issues: Goto, Design before Code, Design Patterns, Corba vs. REST, Object Middleware and ORMs, and Identiﬁers with Spaces.
Dean Wampler specializes in Scala and “big data” analytics using the Hadoop ecosystem of tools. He is a Principal Consultant at Think Big Analytics (http://thinkbiganalytics.com) and the co-author of Programming Scala and author of Functional Programming for Java Developers, both from O’Reilly Media. Dean has a Ph.D. in Physics, but he’s mostly recovered.
Strange Loop is a multi-disciplinary conference that aims to bring together the developers and thinkers building tomorrow's technology in fields such as emerging languages, alternative databases, concurrency, distributed systems, mobile development, and the web.
It's easy to see how this applies to the goto statement.
In regard to the object middleware and the idea of functional 'wrappers', I think that's a completely wrong idea. I don't think the purpose of functional programming is to remove the need for object middleware (or object models) but the idea is to replace object models with a functional models that claim to have better composability, reusablity and closer representation of the problem domain but definitely not in order to gain efficiency. For efficiency you just need to be closer to the solution domain, or in other words, closer to the machine and not use functional nor object programming but C or assembly.
All edges, no body
And remember that these "premature optimization" are going to be maintained by the new intern and you don't want him thinking that a goto would be perfect to fix that stack overflow.