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

Moving Atom to React

blog.atom.io

Post reply on HN
Print view View original

51–60 of 142 posts

Re: Moving Atom to React

#51

Post by girvo »

bronson wrote: post #36
desireco42 wrote: post #4

I finally tried Atom and it looks pretty much like SublimeText, which I use quite a bit. Is there a reference somewhere where it says it was inspired by good work of SublimeText editor? Ah Google always provides: https://github.com/atom/atom/issues/2038

Just curious, is there a reference in Sublime where it says it was inspired by TextMate?

As someone who loved TextMate, ST, and Atom (but now use Komodo): The similarities between Atom and ST are much greater than those between TextMate and ST, in my opinion.

Re: Moving Atom to React

#52

Post by auvrw »

dmak wrote: post #27
donw wrote: post #26

Having spent the past two weeks diving deeply into React, this doesn't surprise me. If you haven't tried it out, give it a go. Being able to rewrite the virtual DOM at will makes development so much cleaner, and it plays incredibly well with other tools, because React is just a presentation layer (I'm using it with Backbone) There are rough edges (TransitionGroup), but they clearly know what they are doing.

Can this play nicely with Angular and still make use of Angular's two-way binding?

if all you're after is two-way data binding and don't necessarily need all the other functionality provided by Angular, it might be worth mentioning that React actually can do that, even though it's not a pattern that occurs that often if you use the Flux application architecture

http://facebook.github.io/react/docs/two-way-binding-helpers...

Re: Moving Atom to React

#53

Post by grandalf »

elwell wrote: post #34
escherize wrote: post #29

Earlier quoted context omitted.

You probably do want an editor that is free, can be used for the rest of your life, works perfectly in a terminal, and is completely programmable. I suggest you continue on with your ascent to emacs understanding! Be sure to use something like prelude, i.e. something with 'sane defaults', and checkout this slideshow by emacs enthusiast (and chief designer of ruby) Yukihiro Matsumoto. ( http://www.slideshare.net/yukih…

I'll check out Prelude; I have better-defaults installed, but this seems to be much more radical. Just curious, how did you find out about Prelude? I'm a freelancer so I don't have any in-person exposure to model/mentor programmers outside of the web, and I'm thus finding it difficult to even know if I'm using Emacs in a sane way. For example of the type of things I wonder about: do most Emacs users keep the basic ke…

also don't forget to take a look at technomancy's emacs starter kit, which was very helpful to me when I got started using emacs:

https://github.com/technomancy/emacs-starter-kit

Re: Moving Atom to React

#55

Post by swah »

swah wrote: post #28
elwell wrote: post #20

Not trying to start an editor war, but I've been trying to learn Emacs for the past week. The learning curve is still at the point of being frustrating/painful. Should I stick with it or download Atom? (Anyone have a solid opinion between the two?)

I use ST because it just works. Let me tell you.. Atom will probably never come close to Emacs programmability and extensibility. Its by far the most beautiful software environment. Its a living thing. In Emacs you're constantly reminded of the love of generations of hackers in improving it. The C-core-and-Lisp-scripting pattern was a perfect match. Emacs has the quality without a name. But Atom is modern. Emacs is s…

Once I wrote an add-on to rcirc, the second emacs irc client. One guy tried and liked it. That made me very, very happy.

This was my only contribution to open source and I wish someday I can feel useful in that way again.

Re: Moving Atom to React

#56

Post by beefman »

I tried scrolling through a 1MB JSON file with all four combinations of React DOM on/off and hardware acceleration on/off. Anything with React on was crashing slow. With React off, hardware accel was maybe slightly better on. Sublime 2 blew Atom away. Chrome had flawless scrolling too (albeit with no syntax highlighting). MacBook Pro running 10.9.3.

Re: Moving Atom to React

#57

Post by lelandbatey »

kolev wrote: post #30

I've used React since it became available and the editor is still pretty slow, to be honest. Can't imagine using it with the option enabled. Honestly, Sublime Text is great, I've purchased a license, but the speed of development will kill it. Every day I "Check Update" and I get disappointed. Not that it needs that much new stuff, but still. You don't feel the heartbeat, if you see what I mean. One great feature of S…

Upon downloading and running Atom, that was also immediately the thing I missed most. I really love the scratch-space as a feature that Sublime Text gives me, and I find that I want it in more and more things.

Re: Moving Atom to React

#58

Post by taeric »

elwell wrote: post #20

Not trying to start an editor war, but I've been trying to learn Emacs for the past week. The learning curve is still at the point of being frustrating/painful. Should I stick with it or download Atom? (Anyone have a solid opinion between the two?)

When you say "trying to learn", what do you mean? If you are trying to dive into everything that emacs can do, I'd imagine you will be in a world of pain for quite a while.

Instead, just use it to edit files. After a while, if there is something you are finding would be convenient, search for and or build it.

That said, some obvious points that you will find nice do come by default if you start out with something like prelude. Though, again, just use it to edit files and don't worry about using the keyboard shortcuts that heavily.

If you are highly motivated by the shortcuts, then I would set a pace for learning a few at a time and really get them down first.

For that matter, whether in emacs or atom (or vim/sublime/acme/whatever), it would be rather instructive to see what features are used heavily by folks. Even better if there was a nice listing for what features were discovered, in order and frequency of use.

Is there already a trend/meme for doing something like this? "What I use in my editor?"

Re: Moving Atom to React

#59

Post by Spendar89 »

dmak wrote: post #27
donw wrote: post #26

Having spent the past two weeks diving deeply into React, this doesn't surprise me. If you haven't tried it out, give it a go. Being able to rewrite the virtual DOM at will makes development so much cleaner, and it plays incredibly well with other tools, because React is just a presentation layer (I'm using it with Backbone) There are rough edges (TransitionGroup), but they clearly know what they are doing.

Can this play nicely with Angular and still make use of Angular's two-way binding?

I think its important to note that React does not encourage two way data binding. Quite the opposite, actually. Data is supposed to flow one-way, from parent to child.

That being said, there's an extension that adds two way bindings, called ReactLink. You can read more about it here: http://facebook.github.io/react/docs/two-way-binding-helpers...

Re: Moving Atom to React

#60

Post by JoelHobson »

lelandbatey wrote: post #57
kolev wrote: post #30

I've used React since it became available and the editor is still pretty slow, to be honest. Can't imagine using it with the option enabled. Honestly, Sublime Text is great, I've purchased a license, but the speed of development will kill it. Every day I "Check Update" and I get disappointed. Not that it needs that much new stuff, but still. You don't feel the heartbeat, if you see what I mean. One great feature of S…

Upon downloading and running Atom, that was also immediately the thing I missed most. I really love the scratch-space as a feature that Sublime Text gives me, and I find that I want it in more and more things.

It's not really the same thing, but there's a scratchpad plugin for Atom that might be useful for you.

https://atom.io/packages/scratchpad

Post reply on HN