4 ms·
It's not fast as what it does though. Opening files takes ages.
by rplnt 10y ago
It's not fast as what it does though. Opening files takes ages.
- taude 10y agoYou don't use it to open a single file for editing, though. Think of it as a lightweight IDE. Use it to open you folder project, which I do once every few days or even per weekly reboot. Once it's up and running - which takes about 5 seconds for my project folder to open on a MBAir - its plenty snappy for editing code. For one-off file edits, like my .bash_profile, nginx conf etc., I still use a terminal-based editor, which is what I'd use on a remote machine anyway.
- rplnt 10y agoSo I would have to use two different editors, customize both, get used to both? That doesn't make sense to me (to be fair, mostly because I rarely have the need for IDE). But if I had, why use a lightweight IDE instead of a "full" one (say Visual Studio, JetBrains *, ...)?
- deno 10y agoIf you don’t need a ‘full’ IDE there’s a lot of mental complexity you can avoid by going à la carte (editor+plugins). It’s easier to add features you care about than learn about a bunch of stuff you’ll never use. That’s very subjective, of course.
- rplnt 10y agoNo, I see what you mean and I guess I agree. But learning how to invoke a feature or installing it should be equal I think.
- coldtea 10y agoThat hasn't been my experience. Programing files open instantaneously. Are you opening 100MB JSON/XML/CSV files? If so, yeah, I guess it's not for that. Or you mean opening some single file ALONG with the editor? That's not how you use such a tool. For casual editing you can always vi.
- rplnt 10y agoYeah, the second case. The problem is that new instance has to start, making it slower to open files than say Visual Studio. I guess that's what I have to take from it - it's a bad file editor and since I edit files I shouldn't use it :)