I still haven't given Atom a go. Is it worth switching from ST3?
Atom 1.0
61–70 of 459 posts
Re: Atom 1.0
#62I really want to like Atom but it's such a pity that they went for CoffeeScript instead of plain ES5/ES6.
Re: Atom 1.0
#63Re: Atom 1.0
#64I really want to like Atom but it's such a pity that they went for CoffeeScript instead of plain ES5/ES6.
Re: Atom 1.0
#65Re: Atom 1.0
#66I really want to like Atom but it's such a pity that they went for CoffeeScript instead of plain ES5/ES6.
Re: Atom 1.0
#67I really want to like Atom but it's such a pity that they went for CoffeeScript instead of plain ES5/ES6.
Re: Atom 1.0
#68I really want to like Atom but it's such a pity that they went for CoffeeScript instead of plain ES5/ES6.
Re: Atom 1.0
#69 ...but realizing the full potential of Atom is about more
than polish. We're considering questions such as: What
does super deep git integration look like? What does
"social coding" mean in a text editor? How do we enable
package authors to build IDE-level features for their
favorite language?
O_o you what?Things I'm interested in ---> A hackable, fast, extensible editor.
Things I have no interest in at all ---> 'Super Deep' github integration, 'social' coding in my text editor.
Dont get me wrong, atoms a great piece of work, and making it extensible for building custom tooling is really great, but what on earth are you talking about?
I hope this is just 'and now we're going to make some plugins' talking...
Re: Atom 1.0
#70Also! I was able to create the colorscheme of my dreams in about 15 minutes, thanks to to the dev tools integration.