Acme was (is?) built by the same people who built Go, and a lot of the same complaints about this way of thinking are heard about Go. Simplicity as a design go

Acme was (is?) built by the same people who built Go, and a lot of the same complaints about this way of thinking are heard about Go. Simplicity as a design goal means that there are trade-offs. YAGNI is one of those trade-offs: "yes we could probably add that feature, but it would make things complicated and we don't think the additional complexity is worth it for this feature". I'm a huge fan of this approach. Mostly because in a majority of cases, YAGNI was true: by thinking more about the problem I needed less language features (as the article says). I'm curious about ACME. I'm annoyed with VSCode (getting too slow), and IntelliJ/Goland feels too Java-y. Vim is fantastic but corrupts my muscle memory, and I can't get past the tutorial for Emacs.