3 ms·

>the only thing noticeably slower to me is start-up That's a big pain point, if you switch between windows (e.g. browsers - including some tabs/incognito for t

by aws_ls 11y ago

>the only thing noticeably slower to me is start-up That's a big pain point, if you switch between windows (e.g. browsers - including some tabs/incognito for testing etc.). After having used eclipse when I moved to ST 3/4 years ago. I realized what I was missing. Faster start time and switching is a must. I normally have 3/4 projects (i.e ST sessions open). And just using key board (ctrl-tab) switch between them, and its almost instantaneous. I typically use it for coding Go, bit of C++ and web UI (javascript etc). The fast feel is so good, that now, I think even if I need to start a Java project, I will try ST with some appropriate plugins.

BinaryIdiot 11y ago
I'm not sure I follow. Start-up time and switching time are two completely different things. In web browsers sure switching between tabs can slow down because they deallocate between them after some time but Atom doesn't do that. Switching is always instant in Atom because it's all kept in memory. I typically have 4-5 Atom windows open all with multiple files open and each has always opened instantly when switching.
- aws_ls 11y ago
  I do understand the difference between start-up time and switching time. I included the latter to tell about my experience with editors like eclipse (and other editors developed in Java). Have not used Atom. Great for you, if you like it. My point being, when I started to use ST (which has been coded in C++). It dawned on me, that most editors not coded in C/C++ (or coded in Java, which are the ones I used) are slow, mainly because of lots of extra memory usage. Using ST also brought back the memories of fast and responsive Vi(m) earlier. I recalled, even MS Visual C++ (which I believe is done in either C or C++), which I used before eclipse/etc was quite fast. Hence my submission. So now, I don't think I am going to like using a coding editor, which is done in any garbage collected language (basically any non C/C++ language). As a side note, when I tried to use the DartEditor for coding in Dart, after having tasted ST, I was thinking why did Dart team not make a simple ST plugin instead? I believe an editor could make a difference in adoption of a new language. In love with ST.

by aws_ls 11y ago

BinaryIdiot 11y ago

I'm not sure I follow. Start-up time and switching time are two completely different things. In web browsers sure switching between tabs can slow down because they deallocate between them after some time but Atom doesn't do that. Switching is always instant in Atom because it's all kept in memory. I typically have 4-5 Atom windows open all with multiple files open and each has always opened instantly when switching.

aws_ls 11y ago
I do understand the difference between start-up time and switching time. I included the latter to tell about my experience with editors like eclipse (and other editors developed in Java). Have not used Atom. Great for you, if you like it. My point being, when I started to use ST (which has been coded in C++). It dawned on me, that most editors not coded in C/C++ (or coded in Java, which are the ones I used) are slow, mainly because of lots of extra memory usage. Using ST also brought back the memories of fast and responsive Vi(m) earlier. I recalled, even MS Visual C++ (which I believe is done in either C or C++), which I used before eclipse/etc was quite fast. Hence my submission. So now, I don't think I am going to like using a coding editor, which is done in any garbage collected language (basically any non C/C++ language). As a side note, when I tried to use the DartEditor for coding in Dart, after having tasted ST, I was thinking why did Dart team not make a simple ST plugin instead? I believe an editor could make a difference in adoption of a new language. In love with ST.