Have they resolved the long-standing performance issues present for the last six months? I've tried using Atom numerous times, but the longer it runs, the less stable it gets.
Atom 1.0
41–50 of 459 posts
Re: Atom 1.0
#42It's super easy to hack on and contribute to.
Re: Atom 1.0
#43The site is severely hammered right now. I'd like to try it again to see if the performance issues have improved.
Re: Atom 1.0
#44Re: Atom 1.0
#45Earlier quoted context omitted.
No, recent patch increased the limit to blazing 4 MEGABYTES!
People editing files longer than that are certainly in the minority.
Re: Atom 1.0
#46The site is severely hammered right now. I'd like to try it again to see if the performance issues have improved.
Re: Atom 1.0
#47what's up with name reuse these days. atom (the syndication format) may be on the verge of becoming obsolete, but it's also forgotten and irrelevant already to warrant a name reuse?
I don't see the problem, they aren't even in the same domain.
Re: Atom 1.0
#48Re: Atom 1.0
#49The killer feature of Atom to me is the ease with which it can be extended (via packages) and the openness to community contribution on core features. That's not a knock against any other editor (some of which share similar characteristics in this regard) – it's just what draws me to Atom. It's super easy to hack on and contribute to.
Might be time to work on some tutorials and examples to make Emacs easier to hack on and contribute to...
Re: Atom 1.0
#50Earlier quoted context omitted.
No, recent patch increased the limit to blazing 4 MEGABYTES!
Without code highlighting though, if I remember correctly. I don't see myself editing a >2MB file containing code, but still...
(You might consider it an abuse of the format, but it is not completely without reason.)
ST3 (well, the plugin for doing it) breezed through prettifying and un-prettifying of the data.