Do the creators of Helix use Helix or other editor or IDE? #15729
|
Hello friends, Why don't you post something on Reddit about your plans for the editor? Thanks |
Replies: 2 comments 5 replies
|
This is quite an insensitive thing to say, IMO. It would be really cool if people would stop putting pressure on maintainers — basically, volunteers — while not doing anything to help the project. Work is being done, look at the commits in the master branch: there is plenty. If you want recent version of helix then compile it yourself. |
Actually I think it is quite an insensitive thing to send people to contribute knowing for sure 99% of PRs will hang in the air without as little as being ever reviewed let alone merged in. Just have a look at PR section above.
There are pretty much zero new features added in those couple-a-week commits you are pointing to. Those are mostly cosmetic. LSP, grammar, color theme tweaks and rust crate version bumps. |
|
I am not saying "you should contribute", I am saying "do not put pressure on people who do the thing they do out of their generosity". People who complain about someone on the internet not meeting their expectations are a common reason for maintainer burnout. In last two weeks, there were a bunch of grammar fixes, LSP integration fixes, and this bug was fixed in the termina library, which is being maintained along with helix (linked issue wasn't marked as closed though). If you don't deem bugfixes to be important, you're objectively wrong. Sure, there is plenty of open PR's. As it turns out, code review takes a lot of time. I don't see anything wrong with the fact that maintainers are picky with what they pull — they have that right. Have your own fork if you're not satisfied with the pace of development — why come complaining to the other people's projects about that? If I sound rude to you two — good. I rather sound rude to someone who only demands, than to someone who does the work that everyone is free to use. |
|
Bug fixes are indeed the most important thing. Better to perfect the existing software first and only then add new features. On the other side there are 1200 contributors. Why are there 1000 open issues? |
|
Why are you asking these questions? Do you think someone has an obligation to answer them? If you want to help an open project like helix: send patches or money. Don't just come in here and loudly wonder why there is so many open PR's and issues and why there wasn't a numbered release in ten months. Doing that just hinders the work that maintainers are doing, and is very demoralizing. |
The question is, how many of these contributors are actively involved in the development of Helix? If I’m not mistaken, you’re considered a contributor even if a pull request you submitted a few years ago to correct a spelling error in the documentation was accepted, and you haven’t been involved in Helix’s development since then. Furthermore, I assume that not every contributor has the necessary knowledge or interest to address every issue. It’s also important to keep in mind that not every issue created actually represents a problem. For example, Helix issues include the “C-enhancement” category. Currently, 597 open issues are assigned to this category. In my view, many of these are feature requests that don’t represent general problems but would be useful for specific users. For example, #15719. I therefore do not consider it meaningful to look solely at the sheer number of open issues. Because there are currently 1,574 for vim and 749 for Kakoune. With 1,632 issues currently, Neovim has even more. Presumably for the same reasons mentioned above. |
|
Yes, I built it to be my daily driver. |
Yes, I built it to be my daily driver.