I was not satisfied with the reasoning used to describe why not to choose helm.
I found two parts to the argument one is that it has "too many features".
Alone this is a very weak argument. An answer would be either disable or don't use the features you don't want/like.
In and of itself, many features is an advantage not a weakness. Now, if this argument were to mention code complexity and bugs that are a consequence of the way many features were implemented then we'd have something here. But there is no mention of this.
The next part of the argument deals with the appearance of helm.
"Upon opening a Helm menu, I am immediately confronted by numerous colors, diagnostics, options, and pieces of help text."
This is also not a strong argument considering that the display of helm can be customized. The appearance alone is certainly not a good reason to justify using selectrum when an established completing framework exists.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4