I think Atom could still have better performance. It wouldn't hurt to have performance tips for package developers too (maybe it has, and I missed them).
Atom 1.0
271–280 of 459 posts
Re: Atom 1.0
#272Earlier quoted context omitted.
Did you miss that you can't create local variables?
WHAT? You mean, you can't declare them without initialization. Oh well, you can't; it's also impossible in Python or Lua. Why is it a bad thing?
Let's not confuse matters here: in both those languages an initialization-assignment will introduce a new binding within function scopes. In CoffeeScript it will always be the parent scope's binding, which means that you must take extra care not to introduce variables used in scopes above, or below, at any given time.
On the other hand, confusing both concepts is bad because it makes it harder to reason about scope, and it has been the cause of much confusion regarding closures in Python and Ruby.
Re: Atom 1.0
#273Earlier quoted context omitted.
My custom Emacs init file that's grown over the years reminds me of my main problem with Emacs: to do anything, it just feels like a bunch of magical incantations using global variables and function calls I wouldn't know how to discover on my own. Random example from my user.el file: (set-cursor-color "White") (setq blink-cursor-interval 0.5) With some trial and error, I could find out if `(setq cursor-color "White")…
I think you'll find that Atom is going to be the exact same, but with Javascript.
No, Atom's API is probably an order of magnitude smaller than Emacs.
Re: Atom 1.0
#274Earlier quoted context omitted.
"The problem is you haven't given a single example of any software that fits the model," Of course not. It's categories of software that have the cycle of bloat. I named three, by implication "text editors" are a fourth. Based on the way people seem to be blinded by the word "bloat" naming specific examples would be seen as an attack, followed by vigorous defenses of how it's not "bloat", which, at least as far as I'…
> Pretty much every text editor ever has started out as a "lean, fast" text editor. And then they grew. Not Notepad. http://notepadconf.com
it's hilarious, my favorites:
> .TXT: NoSQL before it was cool
> Advanced Notepad developer and VIM opponent.
> Hacking Notepad.exe : Using a hex editor to change the blue icon and more
> Workshop: Integrating Spell Checking Into Notepad. Attendees should bring a copy of Notepad, and a dictionary.
Re: Atom 1.0
#275Broke the default font, ugh! Anyone know how to get the old font back?
Just add Inconsolata to your Font Family in Settings. If you want the old font size and line height too, set those to 16px and 1.3, respectively.
Re: Atom 1.0
#276Earlier quoted context omitted.
I disagree with your characterization. Take jQuery for example. 1. Small, fast and minimal. 2. Easy to create plugins. 3. Budding ecosystem and explosion of plugins. 4. Conflicts ensued and some plugins got pulled into the core project. Eventually, the growth of jQuery tapered off as the project stabilized. Not only did the size taper off, it got smaller as well. After nearly 10 years, we're talking about a payload o…
While this is true, and I love JQuery, there's a significant number of JavaScript programmers who do say that JQuery is bloated and slow and old and you shouldn't use it. http://youmightnotneedjquery.com/ and all that. Even if it's not actually true (as you've said, it literally is not bloated wrt filesize) people still think it's true.
Certain things in jQuery are definitely dated & slow. It has a pretty meh implementation of promises, and the .animate library has pretty bad performance. That's why things like Velocity.js exist.
Re: Atom 1.0
#277Earlier quoted context omitted.
Link the GH issue please.
https://github.com/atom/atom-keymap/issues/35
Have you tried this https://github.com/andischerer/atom-keyboard-localization ? Looks like they almost fixed it.
Re: Atom 1.0
#278Earlier quoted context omitted.
None. Atom's installer is a huge download, and the editor is much slower ... It also consumes much more memory and written in coffeescript. Takes a long time to start up ... just a few things on the top of my head. It's a great initiative though so that's already a good point.
I just timed it and it was less than 5 seconds. I would suggest giving 1.0 a spin before you judge.
On this MacBook Pro (MacBookPro12,1) i7(3,1GHz) 16GB of RAM, 512GB SSD ... it takes less that 5 seconds which is way to long for me. If that's ok for you no worries, but you can't say it isn't slow.
Re: Atom 1.0
#279The 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.
Still, there are six "highlight features" right on the home page:
- Cross-platform editing - Built-in package manager - Smart autocompletion - File system browser - Multiple panes - Find and replace
Is it me, or most of these are so basic that of course any text editor would have at least this set from the start? Right, autocompletion came in several steps for Atom, but .. I have used Atom for a while and it seems to understate the real advantages over other editors, such as: it's a GitHub product!
Which brings me to the part where I couldn't stand Atom: I should be able to do any git operation strsight from Atom, no configuration files needed, with a default plugin! Instead, we are left with many community plugins, like git-diff and atomagit. I hope things will evolve in a way similar to autocomplete.