community VS increment-activator

I'd love to try this, though the large number of projects that only support MacOS perplexes me. This excludes at least 80% of people with computers that would like to use your software and effectively limits it to a class of folk with money, creating a sort of nasty exclusivity to the software that does this when there doesn't seem to be a platform-limiting factor.

Their Windows Support Issue was opened on Jun 29, 2022 and the Linux one on the same day, so they're just under two years old. It seems that this isn't source-available right now either, though they mention they'll open source it at some point, but it prevents contributions toward this end too.

The websites this (https://github.com/zed-industries/community/issues/2197) list as the reason for blocking the other OSes though it's quite sparse and doesn't say much.

Genuine and non-argumentative question; why? Easier to focus on one platform for the purposes of achieving good stability before supporting more than one OS, or trying to get a userbase that is typically more willing to pay for your software? Investor pressure?

Most of this is public info btw. You can look at their hackernews/reddit announcement threads or https://github.com/zed-industries/community/issues/52

If anyone wants to express support for windows/linux support, go to https://github.com/zed-industries/community/issues/174 and give it a thumbsup.

https://github.com/zed-industries/community/issues/446

* Added settings to customize the locations and names of journal files ([#479](https://github.com/zed-industries/feedback/issues/479), [#382](https://github.com/zed-industries/feedback/issues/382)).

Zed and Helix are both pretty new.

There's demand for plugin frameworks/scriptability in both but neither of them support it yet. I fully understand why people who need to script their editor are sticking with [neo]vim/Emacs — there are very few other options at the moment.

https://github.com/zed-industries/feedback/issues/388

https://github.com/helix-editor/helix/discussions/3806

- I have used vim for many years (15 maybe?), and once you have passed the initial learning curve (not so terrible, after you keep learning cool stuff even after years of use), it's useful for everything with the same shortcuts. I would actually spend more time learning something else like an new IDE. At the end, I have probably saved a lot of time by sticking to (neo)vim instead of following the latest trend.

- I like terminals because there is nearly nothing disturbing you, and it's usually quick to have something

- there are many little features that looks like nothing but are really really useful when you use them. I'm a big fan of C-a / C-x to increment / decrement a number, coupled with https://github.com/nishigori/increment-activator it's super useful (to change a boolean, a date, a number, etc). The "." to repeat last command, the "*" to search what is under the cursor are other great features. An occasional macro made with "q" may save a lot of time when you need to do a repetitive task, for refactoring for instance, and you can even repeat them according to some patterns with ":g". I'm not sure if those features have handy equivalents on other IDEs.

- I didn't spent that much time doing my config, just adding little changes here and there when necessary, over the years I've got a environment really adapted to my taste.

- I'm currently doing mostly Python, and vanilla (neo)vim is normally good enough, but I'm using Coc (https://github.com/neoclide/coc.nvim) for a little while, and it add a lot of helping stuff easily. Pyright + snippets are useful.

- when something cool happens somewhere else, you often have somebody adapting it to vim. I can use snippets and emmet which are occasionally very useful.

At the end, I don't feel the need to change, it works well, and over the time I could add some neat features to improve it (snippets, emmet, CoC, tagbar, etc). I'm not sure if changing to something like VScodium would worth the time to learn something new (and I like working with terminals).