Threads for am

  1. 5
    jw avatar jw 9 years ago | link | on: Atom: Github is developing a text editor

    AGH! The site is up now! http://atom.io/

    1. 3
      jdp avatar jdp 9 years ago | link

      Looks cool and all, but that config.cson file stood out to me, so I looked it up. It’s CoffeeScript object notation. What is the point of that? JSON is already a poor configuration language, dressing it up in CoffeeScript syntax doesn’t do much to improve the situation. Why not just use YAML?

      1. 1
        jw avatar jw 9 years ago | link

        Yeah, all the language plugins are in that too. I think they’re really just going for consistency–the whole thing is coded in CoffeeScript.

        1. 1
          jdp avatar jdp 9 years ago | link

          Maybe. In that case, it’s weird that it uses Less for theming, I would have thought that Sass made more sense given the rest of the project’s coding style.

      2. 2
        am avatar am 9 years ago | link

        And the blog entry http://blog.atom.io/

      1. 2
        am avatar am 9 years ago | link | on: Atom: Github is developing a text editor

        Sublime Text features + JavaScript instead of Python for plugins would probably appeal to a lot of people.

        1. 2
          dfrey avatar dfrey 9 years ago | link

          Would people really switch to a new editor just because the plugin programming language is different? That seems like a lot of trouble for no benefit.

          1. 1
            qbit avatar qbit 9 years ago | link

            Agreein, There are so many vim plugins you would have to re-write! Maybe adding a vimscript interpreter would lessen the re-write time…. maybe..

            1. 1
              am avatar am edited 9 years ago | link

              JS would definitely lower the barriers to entry on creating plugins, which if the community were large enough, would lead to more/better plugins which would be a big advantage. Of course, the editor itself would have to at least be on par with the competitors.