Hacker News Reader

Comment by GrumpyNl | Hacker News Reader

Nice project but why using REACT for this as REACT is designed for dom manipulation

Well, no it isn't. ReactDOM is designed for consuming the output of React and constructing a DOM-based UI. React itself is fundamentally a reconciliation engine. This is why we've seen React move to such places as React Native (React for native iOS and Android interfaces), React-UMG (React for constructing interfaces in Unreal Engine's Unreal Motion Graphics), React-PDF for generating PDFs, the list goes on. You can view more here:

https://github.com/chentsulin/awesome-react-renderer

Thanks, React for PDF is new to me. I'll check out.

> React itself is fundamentally a reconciliation engine.

Do you know of any good articles / books / videos that talk more about this idea?

This was the first overview I read, and it's pretty good (but incomplete):

https://github.com/reactjs/react-basic

Thanks, I'll check it out.

Yeah - my React/Redux links list has a big section of articles that talk about React's implementation, including both articles that dig into the actual React source and implementation, and many "build-a-mini React" articles: https://github.com/markerikson/react-redux-links/blob/master... .

Thank you!

Not just the DOM.

We use React at Netflix for building our TV app. We moved away from a WebKit stack a few years ago; we have our own retained-mode graphics engine optimized for TV devices so we created React-Gibbon. Besides the developer ergonomics stemming from React, we like the approach it affords us for reaching low-performing devices.

React is a paradigm.

At Airbnb we built a renderer for Sketch that allows us to generate templates for designers with our real, cross-platform, production components (built with React Primitives) https://github.com/airbnb/react-sketchapp

https://github.com/vadimdemedes/ink/blob/master/package.json

It's not using React. "X for Y" is an analogy, as in "it's like React, but for CLI apps!"

> The key difference you have to remember is that the rendering result isn't a DOM, but a string, which Ink writes to the output.

Seems like a pretty easy switch.

The best part about React is being able to declare what your UI will look like instead of constructing it. It's a useful abstraction for any dynamic UI.

I'm guessing the end-goal of this is to be an ncurses replacement. Anything else wouldn't make sense... right?

And why would that make sense? Ncurses has been around a long time and is solid.

It’s hardly elegant to use or reason about though.

Solid and proven and robust, yes.

Different things however.

Doesn't seem to be using react. Just a similar API.

Reply on news.ycombinator.com