Go is not an easy language
Barriers to entry are invisible. They are invisible to people on the inside and most frequently invisible to people who have a hand in creating those barriers.<p>I once had a conversation with a founder about their signup flow. This founder had aspirations to be a global player. They said that step 2 of their flow included entering a credit card number. I had to stop them. &quot;What about people who don&#x27;t use credit cards?&quot; They were nonplussed. &quot;You know, China, much of Africa ...&quot; they had never actually thought about whether people had credit cards because every single person they interacted with had one.<p>Back to languages. If you&#x27;ve never taught an introduction to computer programming for a general audience you are blind to what does and does not matter about a language. You look at things like `foo.bar()` and think &quot;Yeah that&#x27;s a simple method invocation&quot; and have no idea how many people you just lost.<p>Never underestimate how much ease of use matters. We, as a community, have selected for decades <i>against</i> people who care about language ergonomics because they get hit in the face with a wall of punctuation filled text and turn away. We fight over where braces belong while not realizing how many hundreds of thousands of people we&#x27;ve excluded.<p>Ease of use is <i>the</i> most important part of a language. It&#x27;s just that the barriers to entry are invisible and so the people who happen to be well suited to vim vs emacs debates get to talk while the vast majority of potential programmers are left on the outside.<p>We create barriers to entry accidentally because we design for people like us. To us the barriers are invisible.