101–110 of 662 posts
One thing that is conspicuously absent is any mention of it being open source. I can certainly appreciate that Github is for-profit, but I would love to have a clearer idea of how free / not-free this tool will be when it is publicly available.
More data going to Google without opting in first? Bummer.
I can't tell from this page whether it's open source -- I hope it is.
From ##atom IRC: kevinsawicki: is the actual core going to be OS? DouweM: not during the beta How is atom both invite-only and open source at the same time? tyOverby: the engine isn't open source (or at least yet)
For me, this might be the killer feature: http://atom.io/packages/vim-mode
Earlier quoted context omitted.
It's called vim.
I think he means that we need editors that are powerful AND easy to use. Seems like vim isn't really for someone like me (I haven't studied PhD level computer science and I don't write compilers and/or lisp interpreters in my spare time for fun).
Earlier quoted context omitted.
It's built on node-webkit and chromium, which technically works on Windows, OSX and Linux. Do you seriously think they would make an OSX only editor when there's already so many that work on all platforms?
The download is only available for Mac today, but we are working on the Linux and Windows builds.
I am very excited about this, I love the Github team and this looks like a great tool. My only question is -- why should I switch to this from Sublime Text? Are there specific use cases it handles better out of the box, or is it more of a modular base that will be expected to grow and outfeature ST2/3's seasoned plugin economy? I am very happy with Sublime Text now, but I would be willing to switch if either it gaine…
Earlier quoted context omitted.
From ##atom IRC: kevinsawicki: is the actual core going to be OS? DouweM: not during the beta How is atom both invite-only and open source at the same time? tyOverby: the engine isn't open source (or at least yet)
Welp, makes that decision easy. Not making the most important tool in my toolbox one that I can't hack to my liking.
Earlier quoted context omitted.
I don't see a reason to take that as a given. This uses node, ST uses python. Sublime plugins have a huge amount of power and python is certainly not terrible to work in.
I've been playing with it for a few minutes now, and it's definitely the case that it's easier to tweak. Not because of the underlying language, but because they expose so much of what's available through a GUI. I'm blown away by how cool this is. I'm just really hoping for good Vim keybindings and I will pay good money for this once it's out of beta.
Earlier quoted context omitted.
It's called vim.
I think he means that we need editors that are powerful AND easy to use. Seems like vim isn't really for someone like me (I haven't studied PhD level computer science and I don't write compilers and/or lisp interpreters in my spare time for fun).
vim has nothing to do with PhD-level CS or writing compilers and/or lisp interpreters. The Emacs community might fit that stereotype a little more but really not much more.
Vi (vim being 'vi improved') is great because it works on basically any terminal. It works with my iPad's keyboard and with a teletype terminal from the 70s or 80s, as well as a normal PC keyboard. Emacs has similar brags.
The terminal's not going anywhere and if you like keyboard shortcuts, knowing five or ten that will work on any keyboard in existence for an editor that is on most unix systems you'll find has some value.