5 ms·
Logevity seems like a bad single parameter to optimise for. Pick the one you like the most and use it as long as it's available (and as long as you still like i
by jstx1 4y ago
Logevity seems like a bad single parameter to optimise for. Pick the one you like the most and use it as long as it's available (and as long as you still like it).
> I don't want to wake up one day and find out that my favorite editor is getting archived!
The alternative is to never use your favourite editor in the first place, and I can't see how that's better. And it's not like there's a high switching cost, unless you're using something with an actual learning curve like emacs or vim, the transition to another editor/IDE is near instant.
- distcs 4y ago> And it's not like there's a high switching cost I think there is a high price to switching. Once I pick an IDE, I need my fingers to relearn all the different shortcuts for code completion, refactor, find, find regex, find and replace, find and replace regex, code search in different scopes (file level, project level, all open files), start the debugger, debugger shortcuts, launching terminal. The list goes on and on. So I also need to relearn the ecosystem of the editor/IDE. How to configure it? How to install plugins? How to configure the myriad of plugins? How do you codify the entire installation and configuration so that you can push it to Git to make it easier to recreate the same configuration on a new system? Then I need to learn how to configure the editor/IDE for each programming language I'm going to work with. Space/tab conventions, linter configurations, spell checks. Another long list of configurations here. I do find the cost of switching to be high. That's why I ask the questions I do on this Ask HN.
- eric__cartman 4y agoIf you want to maximize for longevity, picking something that existed for 30 years like vi or emacs is probably your best bet.