Earlier quoted context omitted.
Alright, so say they use Spacemacs (Which really should be the Emacs default). Now how would they justify their choice?
I was a happy spacemacs user for a while, but my install kept getting broken by updates. Atom has never just fallen over dead like that. After quite a while it was still mysterious to me how to change simple things or to even trace where certain behavior was implemented. (that can be a problem in Atom too). In short: I didn't have the time. I have a lot of work to do, no time to fiddle. I still miss a few things from…
Atom text editor 1.7.0 released
111–120 of 144 posts
Re: Atom text editor 1.7.0 released
#112Doesn't indicate perf improvements... Not trying to troll, but that surprises me given the large number of complaints about performance.
I'm making a bit of a habit of chipping in on Atom performance complaints with a counterpoint. I've now used Atom as my primary editor for more than a year, and I have no complaints about the performance. This could be because I'm using OSX on recent hardware - I've noticed that my friends using Linux desktops seem to have more issues than I do.
Re: Atom text editor 1.7.0 released
#113Earlier quoted context omitted.
Not sure if you're trolling, because that's a pretty ridiculous question. The obvious answer is Atom's immediate usability and the much easier learning curve over Emacs which requires an incredible amount of research and effort to set up properly and use. For example how long do you think it takes for the average new programmer choosing Atom to figure out and learn to use the fuzzy file search versus them getting tha…
Alright, so say they use Spacemacs (Which really should be the Emacs default). Now how would they justify their choice?
While I'm sure it adds a lot of usability features compared to the default Emacs config and it looks pretty cool, it's nowhere near as immediately accessible as Atom or Sublime - for example, I have no idea how to close an open file without Googling whereas in Sublime or Atom it's either click the "X" or use the standard Cmd-W shortcut. I also have no idea how to open a project or search for a file, and don't really know where to start discovering those things, whereas in both Sublime and Atom you can browse through the menus, or hopefully quickly discover the Cmd-P command launcher which lets you type a command.
If I wasn't somewhat familiar with Vim, I would have absolutely no idea what was going on as by default it uses Vim's modal keybindings. I also noticed an annoying lag when pressing spacebar to bring up the command list thing - slower than any lag in Atom!
It does look intriguing and I'd love to learn to use it more, but I don't think you can really say the usability of Atom/Sublime and of Spacemacs to a new user are anywhere near equal, never mind "how would they justify their choice?"!
Re: Atom text editor 1.7.0 released
#114You know what I would really enjoy? Being able to sign into your Github account and sync your preferences and packages to the cloud. Then if I sign in on a different computer, all my hotkeys, packages and themes are copied over seamlessly. As a crappy workaround I have this: https://github.com/sergiotapia/atom-meteor-packages But still, I would like this to be a core integration. I've since switched to RubyMine and W…
Re: Atom text editor 1.7.0 released
#115Earlier quoted context omitted.
It's alright for small files, but whenever I paste in a huge csv or json file it hangs for minutes. And I use pretty recent macbook pro with high specs. This doesn't happen with other editors.
Same here, I only get issues after around 100MB. Most editors start to struggle at such file sizes, which is a shame, but try loading 100mb into Excel. The only editor I found to work nearly instantly is vi; nano takes almost a minute to load large files.
Re: Atom text editor 1.7.0 released
#116Earlier quoted context omitted.
Alright, so say they use Spacemacs (Which really should be the Emacs default). Now how would they justify their choice?
I downloaded and tried Spacemacs out of curiosity, after seeing your comment. While I'm sure it adds a lot of usability features compared to the default Emacs config and it looks pretty cool, it's nowhere near as immediately accessible as Atom or Sublime - for example, I have no idea how to close an open file without Googling whereas in Sublime or Atom it's either click the "X" or use the standard Cmd-W shortcut. I a…
You can just use the menu bar for that.
>I also have no idea how to open a project or search for a file, and don't really know where to start discovering those things, whereas in both Sublime and Atom you can browse through the menus, or hopefully quickly discover the Cmd-P command launcher which lets you type a command.
You can, as it tells you, use the fuzzy command search by typing M-x. Same as Atom, just a different command.
Honestly, and sorry for sounding rude, to me it just seems like you intentionally tried to not understand in order to prove a point; Just because in your mind you have this idea of emacs just having to be inferior in some way.
As it stands though, it's not.
Re: Atom text editor 1.7.0 released
#117Earlier quoted context omitted.
I've found that when pasting in huge files, disabling syntax highlighting makes a big difference. In fact, if you simply open a sufficiently large (I haven't bothered bisecting the size, but a few megs works) xml file, Atom will disable syntax highlighting by default and the performance will be slow but still usable. If you paste in the contents of a large xml file, syntax highlighting is not disabled and the editor…
Reminds me of old emacs' tricks.
(setq font-lock-maximum-decoration t)
Re: Atom text editor 1.7.0 released
#118Earlier quoted context omitted.
Alright, so say they use Spacemacs (Which really should be the Emacs default). Now how would they justify their choice?
I was a happy spacemacs user for a while, but my install kept getting broken by updates. Atom has never just fallen over dead like that. After quite a while it was still mysterious to me how to change simple things or to even trace where certain behavior was implemented. (that can be a problem in Atom too). In short: I didn't have the time. I have a lot of work to do, no time to fiddle. I still miss a few things from…
>my install kept getting broken by updates. Atom has never just fallen over dead like that.
Could you elaborate on that? This has never happened to me. If this happened because you wrote a bunch of custom layers then I'd argue that it's a non issue because in Atom you cannot do that at all (or at least experience the same problems if you do)
>After quite a while it was still mysterious to me how to change simple things or to even trace where certain behavior was implemented.
As you stated, the same is true for Atom.
>In short: I didn't have the time. I have a lot of work to do, no time to fiddle.
Time for what? The superior modification capabilities in Spacemacs by no means force you to fiddle. It seems to me that all your problems were caused due to you not being able to stop yourself to fiddling with the very sane and good defaults.
This is similar to the argument I see about people who switch to an iPhone all the time. "I just didn't have time to fiddle. I wanted my phone to just work." So just don't exercise your freedom to fiddle then! The defaults in both cases are just as sane and if you some time in the future need to customize something for the sake of productivity, the you can!
Sound to me like somebody moving to China from the US because they "Didn't have time to participate in politics anymore."
Re: Atom text editor 1.7.0 released
#119Earlier quoted context omitted.
I was a happy spacemacs user for a while, but my install kept getting broken by updates. Atom has never just fallen over dead like that. After quite a while it was still mysterious to me how to change simple things or to even trace where certain behavior was implemented. (that can be a problem in Atom too). In short: I didn't have the time. I have a lot of work to do, no time to fiddle. I still miss a few things from…
I don't understand your reasoning here. >my install kept getting broken by updates. Atom has never just fallen over dead like that. Could you elaborate on that? This has never happened to me. If this happened because you wrote a bunch of custom layers then I'd argue that it's a non issue because in Atom you cannot do that at all (or at least experience the same problems if you do) >After quite a while it was still my…
Re: Atom text editor 1.7.0 released
#120Earlier quoted context omitted.
I was a happy spacemacs user for a while, but my install kept getting broken by updates. Atom has never just fallen over dead like that. After quite a while it was still mysterious to me how to change simple things or to even trace where certain behavior was implemented. (that can be a problem in Atom too). In short: I didn't have the time. I have a lot of work to do, no time to fiddle. I still miss a few things from…
> panes https://atom.io/packages/atomic-emacs