Every time I see a new editor come out, I think “I wonder if this will be the one that convinces me to switch away from Vim.” So far none has, but LightTable came close.
There’s also this big hurdle of “I don’t work in the terminal, or provide remote editing capabilities” which most of these new editors don’t ever seem to get.
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?
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.
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.
Intriguing, if cryptic. But from where I sit, this is just a project named “Atom” hosted on Github. Is there any more information on it, something that connects it to Github besides the Github-employed members?
$ whois atom.io
Domain : atom.io
Status : Client Updt+Delt Lock
Owner : GitHub Hostmaster
Owner : GitHub, Inc.
Owner : 88 Colin P Kelly Jr St
Owner : San Francisco
Owner : CA
Owner : US
What are your thoughts on modularity? You see, each component is in it’s own repo and I suppose that you will be able to put those things together to make your perfect editor.
I like this approach, but sadly my current colleges think that it’s useless. They say that it will be a pain in the ass to put it all together and things will break in unpredictable ways.
Every time I see a new editor come out, I think “I wonder if this will be the one that convinces me to switch away from Vim.” So far none has, but LightTable came close.
There’s also this big hurdle of “I don’t work in the terminal, or provide remote editing capabilities” which most of these new editors don’t ever seem to get.
AGH! The site is up now! http://atom.io/
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?
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.
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.
And the blog entry http://blog.atom.io/
There’s a few screenshots in the repositories.
Those look very much like SublimeText with the Soda and amCoder themes.
Sublime Text features + JavaScript instead of Python for plugins would probably appeal to a lot of people.
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.
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..
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.
I wonder if this is an extreme example of work-on-whatever-you-want culture. Perhaps a good GIMP competitor is next, we’re certainly overdue.
Intriguing, if cryptic. But from where I sit, this is just a project named “Atom” hosted on Github. Is there any more information on it, something that connects it to Github besides the Github-employed members?
Answering myself: https://github.com/atom/welcome/blob/master/lib/welcome.md
What is the non-mac equivalent of cmd-shift-P?
ctrl+shift+p
Wow, try clicking on the docs link. It takes you to a GitHub app auth page for your email.
Also worth noting:
What are your thoughts on modularity? You see, each component is in it’s own repo and I suppose that you will be able to put those things together to make your perfect editor.
I like this approach, but sadly my current colleges think that it’s useless. They say that it will be a pain in the ass to put it all together and things will break in unpredictable ways.
http://steve-yegge.blogspot.de/2008/04/xemacs-is-dead-long-live-xemacs.html
Some ideas will keep trying to incarnate for as long as it takes…