4 ms·

One of Go's creator did a lot of the initial coding in Acme[0] :D [0] https://en.wikipedia.org/wiki/Acme_(text_editor) https://en.wikipedia.org/wiki/Acme_(text

• ainar-g 5y ago
  Something tells me that a person who reacts to Vim with a “yuck!” won't like Acme either. Also, I don't know how true this is, but I've read that Acme loses some of its advantages when it's run in e.g. X11 as opposed to its native rio[1] with plumber[2]. [1]: https://en.wikipedia.org/wiki/Rio_(windowing_system) https://en.wikipedia.org/wiki/Rio_(windowing_system) [2]: https://9fans.github.io/plan9port/man/man4/plumber.html https://9fans.github.io/plan9port/man/man4/plumber.html
  • haolez 5y ago
    I _think_ that Rob used Acme in OSX, but I can't find this source.
    • jd3 5y ago
      https://usesthis.com/interviews/rob.pike/ https://usesthis.com/interviews/rob.pike/
• pjmlp 5y ago
  Well, he is also the author, and ACME is even worse than classical VI, in terms of usability. The only thing it has going for it is being based on Oberon's UI workflows.
  • bear8642 5y ago
    Could you expand this? Quite like Acme and wondered what you don't like about it
    • pjmlp 5y ago
      Lack of syntax highlighting for one, not being even half as powerfull as Emacs as second.
• spf13 5y ago
  A couple of the Go authors did a lot of the initial coding and continue to code in Acme (rsc, r). The broader Go team use a wider variety: Vim, Emacs, Goland, and VSCode are the most popular from what I've seen.