Moving Atom to React • Hacker News Board

Re: Moving Atom to React

#41

Post by Igglyboo » Thu, Jul 03, 2014, 12:04 AM UTC

forrestthewoods wrote: post #10

I hope that some day Atom is fast, full of features, and on Windows. My gut tells me it will be a long, long time til it replaces Sublime Text 3 as my editor of choice. =[ Edit: Since several people chimed in with the same thing. I'll check out the windows binaries for. I expect to use ST3 for awhile longer still, at least until Windows is a first class citizen, but this will be great to monitor Atom's development. T…

The pre-built binaries are OSX only but there are instructions for building on Windows and Linux.

Re: Moving Atom to React

#42

Post by yulaow » Thu, Jul 03, 2014, 12:07 AM UTC

rhizome wrote: post #40

spopejoy wrote: post #22

Earlier quoted context omitted.

Emacs is the One True Editor.

Maybe, but ed is the standard text editor.

You are all old, nano is the future!

Other than /s, I wanted to say I am also learning emacs after some years of both vim and st2-3 and I really like it. I have still to stick to a cheat sheet to remember common commands but I am on my way to the Stallmanmination

Re: Moving Atom to React

#43

Post by Sir_Cmpwn » Thu, Jul 03, 2014, 12:19 AM UTC

This is a natural consequence of forcing an editor into the browser. Everything about Atom just seems so unneccessary to me.

What's compelling about Atom that draws people in, compared to Sublime or even vim (my editor of choice)?

Re: Moving Atom to React

#44

Post by willismichael » Thu, Jul 03, 2014, 12:22 AM UTC

hamburglar wrote: post #24

Swizec wrote: post #16

Earlier quoted context omitted.

I just find it funny that replacing "Atom" with "Emacs" in your argument doesn't feel out of place at all. Well, Emacs Lisp might be less newcomer friendly and it's not a webapp. But still, thriving ecosystem - check, accessible to developers - check, huge number of packages - check, runs everywhere - check.

The thing Atom has which Emacs doesn't is that it's approachable even if you don't appreciate all the customization and the rich ecosystem. You can sit down with Atom and just explore it like you would any other GUI text editor, and it pretty much behaves exactly like you'd expect without having to learn any obscure commands or shortcuts. You can learn the commands and shortcuts (and explore the ecosystem) as you set…

That last 10%... same reason I keep going back to emacs after trying a half dozen other editors that more or less promised to be "the one".

Re: Moving Atom to React

#45

Post by ivank » Thu, Jul 03, 2014, 12:23 AM UTC

Typing text at the end of a 1000-line file seems to be laggier with the React-based editor enabled.

Re: Moving Atom to React

#46

Post by cturhan » Thu, Jul 03, 2014, 12:28 AM UTC

After this news, I downloaded and build on windows and yeah it might replace my favorite text editor :)

Re: Moving Atom to React

#47

Post by ReAzem » Thu, Jul 03, 2014, 12:32 AM UTC

tolas wrote: post #3

eknkc wrote: post #2

Just checked the new version briefly. Scrolling performance seems to be much better, especially on a large display with fullscreen editor. Atom is getting pretty decent for daily use.

Haven't been following it too much recently, but just curious, why use it over Sublime?

Atom is free as in freedom.

Re: Moving Atom to React

#48

Post by sehr » Thu, Jul 03, 2014, 12:34 AM UTC

Sir_Cmpwn wrote: post #43

This is a natural consequence of forcing an editor into the browser. Everything about Atom just seems so unneccessary to me. What's compelling about Atom that draws people in, compared to Sublime or even vim (my editor of choice)?

It's very easy to make plugins for. Most web developers know JavaScript, not everyone knows vimscript/viml

Re: Moving Atom to React

#49

Post by orbifold » Thu, Jul 03, 2014, 12:40 AM UTC

sehr wrote: post #48

Sir_Cmpwn wrote: post #43

This is a natural consequence of forcing an editor into the browser. Everything about Atom just seems so unneccessary to me. What's compelling about Atom that draws people in, compared to Sublime or even vim (my editor of choice)?

It's very easy to make plugins for. Most web developers know JavaScript, not everyone knows vimscript/viml

You can write plugins for vim in python, perl and ruby aswell.

Re: Moving Atom to React

#50

Post by shadowmint » Thu, Jul 03, 2014, 12:52 AM UTC

sehr wrote: post #48

Sir_Cmpwn wrote: post #43

This is a natural consequence of forcing an editor into the browser. Everything about Atom just seems so unneccessary to me. What's compelling about Atom that draws people in, compared to Sublime or even vim (my editor of choice)?

It's very easy to make plugins for. Most web developers know JavaScript, not everyone knows vimscript/viml

To be fair you can write vim plugins in python, and a fair number of people do.

It's also, I'd argue, a fail from the Atom guys to make their plugins run in coffee script natively, rather than allowing people the choice of compile-to-javascript/native javascript to write plugins in (this has definitely hurt adoption for the creation of plugins that do more than trivial things or syntax highlighting).

The thing about atom that is compelling for me is apm (the command line atom package manager); its really very good.

(Yes, I know you can write 'pure javascript' atom plugins, but its complex and it's clunky; you have to manually implement the coffee script inheritance semantics. Fail.)