5 ms·
But in some languages bloat is a best practice.
by backlava 11y ago
But in some languages bloat is a best practice.
- bbcbasic 11y agoIt's all about how many adjectives you can get into your class name. e.g. SingletonFactoryAdaptorFacadeProviderEnumerator<BridgeAbstractFactory2_Hack> myClass; With Haskell it is about how big your monad stack is StateT ReaderT WriterT LensifierT MaybeT BeerT (IO Int).
- eru 11y agoMonad stacks are so last decade.
- bulte-rs 11y agoSo this is why the golang community prefers: for c := range(ns) { // some blah }
- rakoo 11y agoThe golang community likes being safe: 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 } until your keyboard keys go off. (and I'm a happy gopher myself)
- eru 11y agoOh, small typo (I think): no parens around (IO Int).
- tl 11y agoI'm not sure that matters either. 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.