3 ms·
I used acme as my main text editor for a few years and a lot of what you say resonates with me. The biggest problem I had with amce wasn't the editor itself but
by uluyol 5y ago
I used acme as my main text editor for a few years and a lot of what you say resonates with me. The biggest problem I had with amce wasn't the editor itself but the lack of easy to use integrations.
Acme integrates well with external programs. This is really nice, but I don't want to spend the time writing all of my own integrations. Maybe I can justify that effort if I work in one codebase for a long time, but I've bounced around and haven't thought the investment would be worthwhile.
Compare with vscode: actively developed and you just click some buttons to get all the integrations. Just so much less friction.
If acme had an active community around it the situation may be different. But that's just not the case.
- coliveira 5y agoThis is an important point: not only the Acme community doesn't want to implement features, they also don't want to share the way things can be automated. This article is a good example: the author spends 90% of the time explaining why things shouldn't be done, instead of explaining how exactly he does it. This is not a great way to create a community.