I sum this phenomenon up as "frictionless development". I don't have to stop and make a decision about something not core to the problem I'm working on while wr

I sum this phenomenon up as "frictionless development". I don't have to stop and make a decision about something not core to the problem I'm working on while writing code. If the default doesn't work for some reason then I can tackle that problem but at that point it usually is core to the problem I'm working on. For some people Go is anything but frictionless though. They spend all their time in Go fuming that their favorite abstraction isn't there. For those people my experience doesn't translate.