December 26, 2016Filed under micro#software development#text editors#tweetstormMarkdown source

I originally posted this as a tweetstorm, but I’m treating this as the canonical and adding a tweet to the end of that “topic” linking back here. Indie web forever.

  • I’ve spent the last couple weeks using VS Code instead of Atom. It has a lot of things to recommend it, especially speed. It’s fast.

  • However, I have to say: it’s painfully obvious to me on macOS that Code is developed by people who aren’t Mac-native. Atom is.

  • And that’s okay—but it means that as many things as I like about Code over Atom, it always just feels a little off to me.

  • Ultimately, what I want is the extensibility promised by both Code and Atom, but with actually native UIs and native performance.

  • So on that note… @raphlinus, how’s XiEditor coming along? Because its approach is what we all really want, I think.

And he replied!

December 24, 2016Filed under micro#rust#software development#text editorsMarkdown source

Tip for doing Rust dev in VS Code: check out this fork of RustyCode, which is currently more actively maintained.

December 20, 2016Filed under micro#software development#text editorsMarkdown source

Things VS Code still needs to fix to be awesome:

  • font-smoothing settings on macOS
  • the color of the status bar
  • ability to cut-to-EOL

And let me turn off the ridiculous smiley-face feedback icon!

To be clear: Code is already very good. But it’s not quite awesome. (It’ll get there.)

December 08, 2016Filed under micro#text editorsMarkdown source

Make VS Code behave a lot more like you’re used to on macOS—get the Emacs keybindings available in CoreText apps here.