Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub's new text editor leaked on Twitter

github.com

Post reply on HN
Print view View original

241–250 of 262 posts

Re: GitHub's new text editor leaked on Twitter

#241

Post by DennisP »

jaredmcateer wrote: post #153
baby wrote: post #95

Earlier quoted context omitted.

I always wonder why I learned emacs over vim. There is never support for it.

Don't feel bad, there's nothing worse (for editing) than using a half baked version of vim in another editor. The best of implementations will leave you with an uncanny valley feeling of disgust. I'd rather use a non-modal editor, all or nothing.

Funny, I'm just the opposite. I'd rather have the basics than nothing.

Mostly I've used VsVim and Viemu. They're both pretty decent. (Viemu is better though, it's got everything I normally use except for :norm. VsVim is missing column mode and the vap doesn't work.)

Re: GitHub's new text editor leaked on Twitter

#242

Post by chipotle_coyote »

Cthulhu_ wrote: post #90
caiob wrote: post #75

Earlier quoted context omitted.

Not to mention the amount of features they'd have to remove in order to comply with Apple's standards.

Would its plugin / scripting library even be allowed? I don't know the specifics of the OSX app store rules.

Based on BBEdit, which does have a version in the App Store, the plugins and scripting would be just fine -- but the CLI integration wouldn't be. (Although you could probably download it separately.)

I don't really see what the advantage of putting ST in the App Store would be, though, for either its developer or any of the users. I like the App Store well enough for certain things, but for developer tools and many utilities the sandboxing tends to be an annoyance at best.

(Also, I don't like that the App Store makes upgrade pricing completely impossible, but that's a whole different rant.)

Re: GitHub's new text editor leaked on Twitter

#243

Post by namuol »

jordwalke wrote: post #22

I really can't wait for this to be released. I am a little pessimistic about the Vim mode. There are countless 80 or 90% complete Vim modes in various modern editors. But the absence of a truly native feeling Vim (that last 10%) is a deal breaker for many. I'd rather see more editor developers spend time finding a solution that provides a truly authentic Vim mode instead of spending countless hours merely approaching…

Maybe just use vim?

Re: GitHub's new text editor leaked on Twitter

#244

Post by rjsamson »

Some interesting new info popping up in the repo: https://github.com/atom/welcome/blob/master/lib/welcome.md - they reference it as being "free during the beta period" - that coupled with a tweet from mojombo yesterday[1] makes it sound like a whole new line of business for them - sounds big!

[1] https://twitter.com/mojombo/status/438200146791129088

Re: GitHub's new text editor leaked on Twitter

#248

Post by drdaeman »

frade33 wrote: post #47

the 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.

Maybe. For node.js devs. And HTML/Markdown/non-programming coders. Not sure about the others.

A good programming editor must treat code constructs as first-class citizens and (at least partially) operate on AST level, not go with typical "hey, we have a bunch of text that we colorize and bracket-match/fold/dissect with some mostly-working regexp mess¹" approach. The latter is just a notepad, not a decent development environment.

As I suspect this editor isn't much different from notepad/textmate/sublime in this regards and it doesn't really understand a thing about the code I'm working on (just pretends it does), it seems quite useless to me.

___

¹) Like this: https://github.com/atom/symbols-view/blob/master/lib/.ctags

Re: GitHub's new text editor leaked on Twitter

#249

Post by pritambaral »

mattw1810 wrote: post #239
pritambaral wrote: post #224

Earlier quoted context omitted.

Seems like they're going the ST route. I'm kinda disappointed Atom won't be open sourced.

It could also mean they are going the Cloud 9 route (unlimited free public editing, limited free private projects) for the web version, which would essentialy be the same as their current subscription model, while still open-sourcing the editor itself.

Cloud9's open source edition has a few features missing, most notably realtime collaboration.
Post reply on HN