Earlier quoted context omitted.
There is freedom of choice. You don't have to use it.
Still, he is entitled to his opinion. You don't have to downvote it. :>
Sure
GitHub's new text editor leaked on Twitter
191–200 of 262 posts
Re: GitHub's new text editor leaked on Twitter
#192Guess, github bought sublime.
Re: GitHub's new text editor leaked on Twitter
#193Looks amazing, but why CoffeeScript?
Because it's a modern and usable version of one of the most ubiquitous language of the modern web era (and happens to actually produces that language as an output, making it seamless to integrate)?
Coffee-script is just synthetic sugar with some build in constructors for syntax elitist like rubyist or pythonistas, it not any different than using plain js. It does not save you for the quirks of js or give you any "improvement" beyond the syntax. Is a nice language, but don't put i like is something more of what it is.
Re: GitHub's new text editor leaked on Twitter
#194Earlier quoted context omitted.
> For instance, I love to bind "s" to "go into insert mode, insert one character, exit insert mode". Doesn't that already exist, by hitting 'r'?
That replaces the character under the cursor, it doesn't insert a new one.
Ah, thanks for the clarification.
Re: GitHub's new text editor leaked on Twitter
#195the next big thing for devs. I love sublime and will, but can't figure why is it taking them so long, to launch it on mac appstore.
Because?
Re: GitHub's new text editor leaked on Twitter
#196Am I the only one who finds it hard to believe this has indeed been leaked and is not just a marketing strategy from Github? The repos are not even private.
Leak is the wrong term, and it’s doubtfully a deliberate marketing move either. More like, “suddenly being noticed because a bunch of GitHubbers followed the @AtomEditor account on Twitter”.
Also, despite the plethora of repositories, the actual editor is not available. It could be many of the public repos are public so they can be installed using their Atom Package Manager, which would likely have to jump through hoops if they were private.
Re: GitHub's new text editor leaked on Twitter
#197If you go to https://atom.io/docs you can authorize the app with your github account. You still get the 'soon' page afterwards, but at least you're now something like an early atom.io beta user ;)
Re: GitHub's new text editor leaked on Twitter
#198There's a bunch of lovely gems scattered through the Atom repos. Some of my favorites from a first quick glance: Biscotto — A CoffeeScript API documentation generator based on TomDoc notation: http://atom.github.io/biscotto/ React-Coffee — A little glue that makes Facebook's React easy to use from CoffeeScript without having to resort to JSX: https://github.com/atom/react-coffee SpacePen: A minimalist view library fo…
I'm confused, why would they be working on React and SpacePen? Don't they do (roughly) the same job?
I have a feeling that started out looking at React but opted to go with SpacePen for some reason.
Re: GitHub's new text editor leaked on Twitter
#199Earlier quoted context omitted.
You're talking about Emacs, right? Over the last 18 years, I've tried to figure Emacs out a few times, but it always ends up baffling me. It may be as powerful as you say, but given how obtuse I am (or perhaps how terrible Emacs is), I'll never know.
It took me a good 15 years before I started using Emacs a few months ago. What made it work was (a) learning how to tweak the configuration to suit me, (b) learning Emacs jargon equivalents (chiefly: selection => region, cursor => point, open => find, file => buffer, pane => window) and (c) already knowing enough lisp to be able to tweak configuration further than simple variables and modes. Then what really made it…
> It is, however, still weak with languages that heavily rely on IDE support, like Java and C#
Which I see as a weakness of those languages -- not a weakness of Emacs (or Vim, or any other Not-The-Walled-Garden-IDE). I think needing an IDE to be productive is a kind of "language smell".
I do appreciate that some of us don't have a choice but to use them, and that they have good points -- just not this.
Re: GitHub's new text editor leaked on Twitter
#200Earlier quoted context omitted.
Some more screenshots * https://f.cloud.github.com/assets/671378/2265086/c6897dba-9e... * https://f.cloud.github.com/assets/671378/2265022/bb148a20-9e... * https://f.cloud.github.com/assets/2988/1796891/85e69ff2-6a93... (animated gif) * https://f.cloud.github.com/assets/671378/2241795/ba4827d8-9c... * https://f.cloud.github.com/assets/671378/2241819/f8418cb8-9c... * https://f.cloud.github.com/assets/671378/2241519/04…
Some more... * https://atom.io/assets/screenshot-main@2x-e0b7c5a0be2ef13348... * https://atom.io/assets/screenshot-native-web@2x-2842562f4757... The second seems to confirm this being web based.
It confirms it as being Webkit based, but not necessarily that it is running on the web.