Hacker News Reader

Comment by backlava | Hacker News Reader

But in some languages bloat is a best practice.

It'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).

Monad stacks are so last decade.

So this is why the golang community prefers:

    for c := range(ns) {
        // some blah
    }

The 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)

Oh, small typo (I think): no parens around (IO Int).

I'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.

Reply on news.ycombinator.com