5 ms·
Atom is so slow it's a sideshow. It also has the problem of jEdit and Komodo, not a native app so they greatly reduce battery life on laptops. Just because Sub
by bluedino 11y ago
Atom is so slow it's a sideshow. It also has the problem of jEdit and Komodo, not a native app so they greatly reduce battery life on laptops.
Just because Sublime's developer isn't updating it as much as he used to doesn't mean anything. What more could you want? The community hasn't stopped with plugin development which is what really counts.
This just reminds me of the consumer software mindset where a new version needs to come out every year, just for the sake of it. There's nothing wrong with using 'old' software that just works.
- melling 11y agoThen you apply an exponential curve and one day the much larger development community and Moore's Law push Atom past Sublime. https://en.m.wikipedia.org/wiki/Exponential_growth https://en.m.wikipedia.org/wiki/Exponential_growth Note, I own Sublime and still use it. However, I do see great value in the Atom project. Developers shouldn't fall in love with an editor. Key bindings perhaps. The ideal editor would let me turn it into vim or Emacs, for example.
- kuschku 11y ago> The ideal editor would let me turn it into vim or Emacs, for example. You mean like vim-mode is already existing in every editor worth to be called editor?
- melling 11y agoNo, I mean an editor that allows you to build a complete vim with macros, for example. The source for vim wouldn't be in C and you could implement plugins like EasyMotion. https://github.com/easymotion/vim-easymotion https://github.com/easymotion/vim-easymotion
- Luc 11y agoAtom's pretty good for that, or am I misunderstanding you? https://github.com/atom/vim-mode https://github.com/atom/vim-mode https://github.com/leny/atom-easy-motion-redux https://github.com/leny/atom-easy-motion-redux
- juandazapata 11y agoCome on. The only and true vim-mode is vim. Other implementations are just pity attempts so far.
- coldtea 11y agoOnly if you want all the stuff (including crap) that vim offers. If you're OK with the 50-100 core commands, then those emulations can be perfectly fine. (Also some of us used vi too, and that didn't have all the stuff vim comes with either).
- 1000cuts 11y agoImprovements in single-core performance (the kind that matters for Javascript and most real-world applications) has been near-stagnant for many years now. Your projection also implies that programmers of the future won't also produce exponentially slower code. I have doubts about that, considering how unresponsive programs these days are, compared to their counterparts of two decades ago (when most programmers actually cared about performance).
- coldtea 11y ago>Then you apply an exponential curve and one day the much larger development community and Moore's Law push Atom past Sublime. First, there are no more free "Moore's Law pushes". There haven't been any to write home about for at least 2-3 years. It's now all about multicore (which is also not exactly the best thing for a JS based editor to benefit from). Another issue is that JS performance has already reached most of the optimizations out there. With the JIT-based JS engines there has been a 100x or more speedup from early JS to circa 2010 or so. Not it's at best some 20%-30% speedup year over year, and that only in some narrow cases. Even webassemply (when that lands as a viable option) is not expected to change that much. As for the larger developer community, ST already has a huge development community for plugins -- which is where most of the action happens. And sometimes a talented programmer with a strong opinion can be better than "design by comitee". That said, I find Atom to be a nicely designed editor which would have a great potential, if only it wasn't burdened with a crappy architecture and runtime choices. It might not even be JS fault, as Microsofts VS Code seems to do much better.
- melling 11y agoMoore's Law isn't over. You are asking us to believe the recent past means that we will not get more single cpu performance increases over the next 10-20 years. And you're saying that a 20%-30% (6x-13x) improvement over then next 10 years won't make a big difference? If Atom was 10x faster, would it be more useable? As for concurrency not being applicable, that might be true for some tasks but I can easily imagine scenarios where is would help greatly. Multiple buffers and files. Replace and search for example. Indexing, concurrent garbage collectors, ... So, in your scenario, if cpu's only become 10x faster and we get 60 CPUs, we won't be able to make a better editor?
- coldtea 11y ago>Moore's Law isn't over. The "transistor count" version of Moore's Law has been saved by multiple cores. The speed version hasn't been true for single core performance for years. > You are asking us to believe the recent past means that we will not get more single cpu performance increases over the next 10-20 years.* Moore's law is put in specific time terms -- transistors/power(speed) should double every 18 months. So if this hasn't been the case for the recent 2-3 years, then Moore's Law is already broken -- no belief required. The fact that it's very possible we'll might see another CPU speed breakthrough in, say, 2022 or 2028 or 2050 doesn't change that -- as Moore's Law talks about sustained improvements over 18 month periods. Besides, few in the industry disagree that the Moore Law is pretty much over. That's a great motive behind all the talk of optimizing multicore performance, functional techniques etc. >And you're saying that a 20%-30% (6x-13x) improvement over then next 10 years won't make a big difference? If Atom was 10x faster, would it be more useable? As already said, this 20-30% is "at best" and covers specific benchmarks and uses, not general speed. And nobody said this is sustainable long term either. After a JIT engine reaches a specific point of sophistication, there are few things that one can add to make it even faster.
- phragg 11y ago> There's nothing wrong with using 'old' software ... And this is why I'm on ST2
- donatj 11y agoST3 took me a bit to get set up, I stuck with 2 for a long time, but I would say the upgrade was worth it. Faster, more stable. Big fan.
- coldtea 11y agoSure -- though ST3 has been rock solid for me (on OS X -- mainly using JS, PHP, Python and Go related plugins) for 2 years or so.
- arm 11y agoAlthough, keep in mind (in my experience at least), Sublime Text 3 is way faster than Sublime Text 2.
- jackhack 11y ago>>What more could you want? Printing. I'm not the only one to feel this way. https://www.google.com/search?q=sublime+text+printing https://www.google.com/search?q=sublime+text+printing Atom users, too: https://discuss.atom.io/t/printing-support/760/8 https://discuss.atom.io/t/printing-support/760/8
- untog 11y agoYou might not be the only one, but I'd wager you are in a tiny minority.
- wlesieutre 11y agoI'll admit I didn't even realize that Sublime couldn't print. Been using it for years and I've never tried once.
- BinaryIdiot 11y agoWhen I was doing DoD work being able to print code was amazingly important since it's not always easy to bring computers / files into certain environments but paper? Yeah pretty important even to this day in that area. Now that I stopped doing DoD work I literally have zero use for it.
- deleted 11y ago[deleted]
- amichal 11y agohttps://packagecontrol.io/packages/2pdf https://packagecontrol.io/packages/2pdf is what i use in ST2 not sure about ST3
- BinaryIdiot 11y ago> Atom is so slow it's a sideshow. It also has the problem of jEdit and Komodo, not a native app so they greatly reduce battery life on laptops. Granted I would expected it to be slower using an interpreted language and all but other than opening large files the only thing noticeably slower to me is start-up. That's it. The plug-in ecosystem got me to permanently switch to Atom and it's very fast. I also haven't noticed any battery issues yet as I still will frequently use my MacBook for sometimes most of a day before needing to charge. I'm not sure if you were speaking from experience with Atom or just approximating but it's surprisingly good. I know I was extremely skeptical to the point of calling it a dumb idea to write an editor in the way they did but after they dumped react I don't notice any slowdowns.
- 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 agoI'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 agoI 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.
- funkyy 11y agoI dont get why people only discuss Atom vs Sublime. Is programming world in such a need for A vs B discussions again? There are probably at least 5 text editors for coding worth checking out. There is Brackets as well, which I am using with no problem since 6 months. The core program has not failed to do its job even once during this time. No crashes, stellar performance. So if you annoyed by Atom and not sure about Sublime and its cost - try Brackets. I bet you you will love it.
- PeCaN 11y agoPerhaps it's because Atom sort of bills itself as a hackable, JS/HTML version of Sublime. It's a very apples-to-apples comparison, while Brackets targets a particular niche and isn't as directly comparable.
- sargas 11y agoIn addition, Visual Studio Code is another editor that is competing for space in the dev world.
- netghost 11y ago> There's nothing wrong with using 'old' software that just works. That's why I use TextMate ;) Honestly, it's got a great UX and is native for OSX. But hey, use whatever you enjoy.
- JustSomeNobody 11y agoYeah, it's ridiculous that even developers can't just let software be "done" (save for a few bug fixes, etc.).
- softinio 11y ago> Atom is so slow it's a sideshow Thats a bit over exaggerated. As fine for me. Maybe I have a faster laptop
- lobster_johnson 11y agoYou might not realize you want something until you have it. Switching to Atom a few months ago let me get things linting errors displayed inline [1]. Sublime plugins have very limited ability to tweak the editor contents. There's also a neat Git plugin that turns Git's textual conflict markers into live markers allowing you pick which side to use. It also displays a list of pending project-wide conflicts while you're working — also not something Sublime plugins can do. The Markdown Preview package is very nice. It displays a preview window inside Atom. Sublime can't do this because of the API. Atom has a bunch of Go packages that autoformat on save, provide "intelligent" autocompletion (e.g. type a variable and a dot and it will suggest methods callable on the variable), lint/syntax check, and so on. (In particular, Atom's autocompletion mechanism is extensible; plugins can provide completions based on context. Sublime's autocompleter is hardwired, I believe.) There are some Go packages for Sublime, but they never worked properly for me. The ones for Atom are quite polished and just work. Sublime plugins can't modify the file sidebar. With Atom, I can have the sidebar colorized based on Git status, for example. The color-picker package is great — when editing CSS you can get a little color picker popup for color codes. Again, not possible in Sublime. In short: Sublime has a very limited plugin API that supports very little side from editing text. Atom's API opens up a ton of possibilities that simply can't be done in Sublime. [1] http://i.imgur.com/hlIwg5J.png http://i.imgur.com/hlIwg5J.png
- x0 11y agoActually, there is a colour picker plugin in Sublime. I haven't used Atom's so I don't know how it compares. http://i.imgur.com/NZOad6T.png http://i.imgur.com/NZOad6T.png