3 ms·
Just up thread from your comment, someone commented in a positive way on the infinite customisability of vi. So which is preferable - customisability or very l
by saimiam 2mo ago
Just up thread from your comment, someone commented in a positive way on the infinite customisability of vi.
So which is preferable - customisability or very limited feature set?
- kelnos 2mo agoI think the problem with the vi/vim example is that it's very much not for everyone. I use it, and have used it for 25-odd years, but I'm not an expert at it by any means (because I haven't taken the time to try to be), and occasionally have to look up how to do something. But I've customized it to my heart's content, and feel very productive in it. But I would not expect a large percentage of developers to want to do that. I've used IDEs as well, and they're mostly fine, and work really well for lots of people. Many IDEs are pretty damn customizeable too, though most people may not change many settings.
- ozim 2mo agoQuestion is: what are you building? There is no general answer that will answer which is preferable. It is easy for people to come up with features they want or a customisation and they don't care for the cost of actually maintaining that feature or customisation. I work on building SaaS platform, we had multiple customers for whom we build custom features and they paid for development of those features. Not fun part is after 2-3 years those customers are gone (for example employees at customer rotated and they switched to something totally different) — but now we are left with dead feature no one is paying for supporting, some are easy to remove, some are not.