1. 20

  2. 15

    My early thoughts on Atom: it seems developers only use newish Macs.

    1. 7

      My early thoughts on Atom: no way in hell am I going to build up habits or muscle memory for a (nother) proprietary editor. I may be stupid but I’m not that stupid. What happened to the time I spent learning how to use WordStar, Turbo C++, Visual C++, and Epsilon?

      Also it’s kind of shitty that they took the Pie project’s name.

      1. 1

        Exactly! And the fact that my “editor” is not just for inputing text, but is the executive of my software-development processes. I use both Emacs and Eclipse, but not interchangeably. They are each used for different kinds of programming; immediate interactive coding for Emacs, refactoring, expansive multi DSL programming in the large for Eclipse. They both require access to the file system, support for multiple DSL, remote machines, data source, ability to launch application, monitoring consoles/buffers. None of it can be accommodated with a web-based text editor. Even if it’s open sources someday, I don’t think its technology will ever accommodate my needs without a major rewrite.

      2. 3

        The conclusion under the “Is It Worth All of the Hype?” heading seems spot-on. However, due to the amount of time the average programmer spends inside their editor, the constant effort to optimize the whole process around editing code does make sense as long as it doesn’t turn into an obsession.

        1. 12

          While this response will sound snide and cynical, I try to give myself as little help as possible in writing code. “The horror!” you scream. But no, I want to make it hard to write a lot of code so my solutions are as small and simple as possible. Nice editors make writing a lot of code easy, which is in direct opposition to reading code, the most important aspect of programming.

          1. 4

            Oh, I see where you’re coming from, and I do agree with you to a certain extent. But, there are improvements to be made outside of helping one write long and needlessly complicated code – e.g. playing nicely with other tools (LightTable’s leiningen integration), automating processes (integrating build systems), and integrating docs.

            I’m sure not all of it will be everyone’s cup of tea, but I know some of them definitely help me in day-to-day tasks.

            1. 3

              You can pry vim from my cold dead hands because it’s a good editor. It’s not much for creating code (no autocomplete or snippets or whatever people use these days), but it excels at taking code that’s broken in some form (either buggy or in need of refactoring) and letting me whip it into shape with minimal hassle.

          2. [Comment removed by author]

            1. 1

              I’ve written a post on their discussion site about the Deuce editor architecture from the Dylan IDE. Deuce was a descendant of ZWEI, a precursor to GNU emacs. This architecture would also help them solve some of their current performance and memory usage problems.

              The post is here: http://discuss.atom.io/t/the-deuce-editor-architecture/2218