4 ms·
Is it just me or does the way the lack of features is used as a feature here seem like the 'your holding it wrong excuse'. Just from this essay and never having
by smegger001 5y ago
Is it just me or does the way the lack of features is used as a feature here seem like the 'your holding it wrong excuse'. Just from this essay and never having used Acme, I wonder what advantage the has over other minimalist text editors. I mean if lack of features is the feature why not just use ed.
- Avshalom 5y agoThat specific phrase came to my mind too. On the other hand sometimes people are just holding things wrong.
- zozbot234 5y agoThere's something to that criticism, but plan9 was also built for improved modularity and compositionality when compared to earlier Unix. Some features that are not included in Acme may be achieved simply by leveraging outside code.
- marcus_holmes 5y agoAcme 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.