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

61–70 of 142 posts

Re: Moving Atom to React

#61

Post by _greim_ »

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'm not an expert but I think you wouldn't really want to do this as they both want sole control of the chunk of DOM in question.

Re: Moving Atom to React

#62

Post by shurcooL »

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)?

> compared to Sublime

It's open source; Sublime isn't. I can't do anything to make Sublime better.

Re: Moving Atom to React

#63

Post by baddox »

jshen wrote: post #21
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.

atom works well out of the box. Emacs ... not so much.

How often do most developers set up a new environment? For me, it's nowhere near enough for me to care at all whether my main development tool "works out of the box."

Re: Moving Atom to React

#64

Post by kristofferR »

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.

Yeah, since this is generally how things work in OS X it makes Atom feel quite ancient to me.

It's such a major step in the wrong direction to have to go back to trying to avoid shutting down applications/your computer since it's such a big hassle.

If I want save something I'll save it and if I want to close something I'll close it, just keep it "open" for me in the mean time.

Re: Moving Atom to React

#65

Post by rdtsc »

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?

Look at some of Peter Hunt videos:

https://facebook.github.io/react/docs/videos.html

2-way binding is not necessarily the way to go with this.

Re: Moving Atom to React

#69

Post by seanp2k2 »

mproud wrote: post #68

A 2 MB file limit makes Atom just impossible for me to use.

Curious: what type of things would you want to edit over 2MiB? I think it's probably more a function of "having such a huge DOM would be a bad UX anyway" vs just some arbitrary limit.

Re: Moving Atom to React

#70

Post by exogen »

The new rendering method kills subpixel font rendering, I suspect due to the translate3d hardware acceleration. Unfortunately noticeable for those of us not yet on retina-resolution screens.
Post reply on HN