HNHacker News
TopNewBestAskShowJobs

GeordiePowers

18 karma · joined November 7, 2018

submissionscomments
GeordiePowers··on The pros and cons of placebo buttons
In Toronto, most of the buttons have long done nothing to control the light cycle, and only trigger the audio crossing indicator. Lately they've been replacing the signs signs on these, with each now saying "Button for audible signal only". Good way to re-purpose the existing hardware.

See here for a comparison of old vs. new https://i.imgur.com/a0FXI5c.png

GeordiePowers··on Atom 1.33
Huh, I didn't even know there was an ex command for undo. Neat. I imagine that would be a pretty easy PR to the ex-mode package, if you're up to it ;)
GeordiePowers··on Atom 1.33
The vim plugins in atom completely blow VSCode's out of the water. It's split up into two packages ('vim-mode-plus' for most of vim, and 'ex-mode' for handling ex commands), but they work together very well.

In my experience (which certainly does not reflect everyone's), Atom wins in performance these days, too. Startup time is a bit slower, but once it's running it's quite snappy. It feels... less like a webapp than VSC does, if that makes sense.

GeordiePowers··on Atom 1.33
atom-ide (https://ide.atom.io) brings a lot of the great intellisense features over to Atom. It's most likely not completely on par, but as far as I can tell and based on my own usage, it's beyond good enough for most work.
GeordiePowers··on Atom 1.33
I switched, after a prior history of many other editors, to VSCode, and then to Atom. One main reason: the vim plugin. The VSCode one was (is?) just not good. Atom's is quite good.

VSCode is better for most people; it's a great editor, and does more out of the box without configuration. However, if you're someone who DOES feel the need to tweak everything until it's just right, VSC doesn't hold up. JSON configuration is just clunky. Atom is, at least in some aspects, scriptable without the need to build a full plugin (though it's certainly no emacs), and that's quite valuable. And, when you introduce the atom-ide package, the gap in completion and debugging functionality between the two gets quite a bit smaller.

Also, anecdotally, Atom seems to have had better performance across my machines; especially on lower-end hardware. I'm only working on small-medium sized projects, so this might just be me.

GeordiePowers··on Ask HN: Is Visual Studio Code the Emacs of 21st century?
VSCode isn't anywhere near "open" enough (plugin APIs may be lacking). For example: the VSCode vim plugin is one of the worst of any major editor, while the Emacs version (Evil) is arguably the best implementation of vim period.

Atom is much closer to Emacs; nearly all the functionality is provided through optional packages, and it's very open to little tweaks to make it just the way you want.