SingletonFactoryAdaptorFacadeProviderEnumerator<BridgeAbstractFactory2_Hack> myClass;
StateT ReaderT WriterT LensifierT MaybeT BeerT (IO Int). for c := range(ns) {
// some blah
} a, err := doFirstThing()
if err != nil {
return err
}
b, err := doSecondThing(a)
if err != nil {
return err
}
c, err := doThirdThing(b)
if err != nil {
return err
}
(and I'm a happy gopher myself)
Let's say you're talking about Java. A "bad" team will have mountains of code. A "good" team will apply Greenspun's Tenth Rule and use a lisp to compress down the mountain to the extent that "lisp" can compress it over Java.
You may protest that the lisp has angle brackets and that it's inferior to say Clojure, but the machine does not care.
The kind of org that cares about how it writes software will choose the right tool for the job, which may be Lisp. However they may be able to achieve their aims in Java. Whatever they choose it would have been carefully considered.
The kind of org that doesn't care how it writes software is unlikely to choose an outlier language and will use C#, PHP, Java etc. because it is easier to hire devs and you won't get fired for choosing it.