12 ms·
React-basic: Description of the conceptual model of React
- firasd 9y agoI think by now many HNers will have grasped the idea behind "The core premise for React is that UIs are simply a projection of data into a different form of data", but here's a related good read from around the time this was written: Pure UI https://rauchg.com/2015/pure-ui https://rauchg.com/2015/pure-ui Also of interest, the classic 'Rethinking best practices' presentation: https://www.youtube.com/watch?v=x7cQ3mrcKaY https://www.youtube.com/watch?v=x7cQ3mrcKaY
- seanmcdirmid 9y agoThe problem with retained mode UIs is that they lose the ability to continuously translate data with functions. Immediate mode UIs don’t have that problem (since you are just drawing to the screen on each frame), but suffer from efficiency problems (not to mention you have to do your own layout). Databinding (e.g. as in WPF) allowed some of these transformation to occur declaratively, but were too inexpressive in general. React is a nice new point in the space, and is much more pragmatic than FRP or Rx.
- davedx 9y agoYes, React is an interesting middle ground that hits a sweet spot for many classes of web apps. Try and make (real time) games with it and you soon realize that despite it being a good conceptual model, you really need to be in an immediate mode rendering mode. Does anyone know of any immediate mode game engines using concepts from React?
- seanmcdirmid 9y agoImmediate mode is really the sweet spot for games, I still do most of my experimental UIs using immediate mode on top of canvas for that reason. If you need to write something like a code editor, it is just much easier than fighting the DOM (you can easily do your own caching using images), though you have to roll a lot on your own. The problem with gaming is that you usually don’t want to use the DOM, and React’s value add is mostly in its DOM handling.
- nervestaple 9y agoI'd be curious to know too -- I've been working on a custom React renderer for the Phaser webgame engine after dealing with a lot of frustration around state management in Phaser. (https://github.com/nervestaple/react-phaser-kit https://github.com/nervestaple/react-phaser-kit) I know there are similar parallel approaches like https://github.com/FormidableLabs/react-game-kit https://github.com/FormidableLabs/react-game-kit and https://github.com/michalochman/react-pixi-fiber https://github.com/michalochman/react-pixi-fiber. You can sort of use them in immediate mode by calling setState inside the update loop, but the abstraction leaves a bit to be desired...
- deleted 9y ago[deleted]
- swyx 9y agoSo I've never done game dev - can anyone explain what immediate mode rendering is like to a React webdev?
- untog 9y agoIn the simplest way possible, it would be like running this.element.innerHTML = "new value" instead of this.setState({text: "new value"}) React's method of async state setting is really great when you have a bunch of components that know little to nothing about each other, because it'll automatically batch things up. But in some situations, and games are a perfect example, you need the value to change right now.
- seanmcdirmid 9y agoActually, that looks like retained mode. Immediate mode simply means you specify what to redraw on every frame, there is no caching unless you specify it. And you basically redraw whenever some state changes (in a game this is going to be at frame rate). In React, when some state changes, you respecify the DOM for components whose state has changed, but asynchronously the library determines how to make the DOM update more efficient on the next frame redraw.
- swyx 9y agothanks, what is the benefit of no caching then? seems fairly wasteful if you have an engine capable of rendering at frame rate already.
- seanmcdirmid 9y agoSimplicity. Retained-mode means you modify the scene graph (aka DOM) using imperative statements, it is difficult to keep your UI in synch with your models. With immediate-mode, you simply create a function f(m) over your model m to render it on each frame rate (which also often involves imperative instructions affecting the frame buffer, but the buffer can be cleared on each frame so who cares). Retained-mode caches by default (often in opaque ways), which was the whole point (only re-render parts of the scene that have changed). You can roll your own caching for immediate mode, usually via some kind of invalidation scheme (use image for a node if nothing changed for this component, otherwise call that node's re-render method). On the other side, projects like React takes the retained-mode DOM and make it look more like an immediate-mode abstraction without sacrificing so much performance.
- swyx 9y agooh wow i thought this was interesting but surprised this is front-page of HN interesting. So this is written by Sebastian who is part of the React core team. A lot of the earlier stuff might seem obvious to most but I think it gets increasingly non obvious as you go down the list. I would direct your attention to the bit at the bottom on Algebraic Effects (https://github.com/reactjs/react-basic#algebraic-effects https://github.com/reactjs/react-basic#algebraic-effects) - that came up on twitter today in relation to what the mental model behind React Suspense is (even though technically JS doesnt have Algebraic Effects itself, thats kind of what they are trying to do with async rendering.) I'll let gaearon and co explain better if they see this, I don't want to butcher it.
- deleted 9y ago[deleted]
- Benjamin_Dobell 9y agoThere's already a gazillion React templates out there, all of varying quality. Nonetheless, in case anyone is interested, here's a modern (Babel 7, Webpack 4) React SSR template we developed for internal use, but have subsequently open sourced: https://github.com/glassechidna/practical-react-ssr https://github.com/glassechidna/practical-react-ssr I don't think there's anything particularly revolutionary in there, it's just a reasonable starting point to hit the ground running.
- Benjamin_Dobell 9y agoOut of curiosity, would people mind elaborating on the reason for the down votes? If you've looked at the template and there was something you thought to be sub-standard, then I'd love to know what people would do differently. If the down votes were because I made another React template, then, ah, that's somewhat understandable. Although, as I've stated, it was created for our own internal use, and was simply open sourced because we love open source and giving back to the community. Additionally, at the time of creation there absolutely weren't any full-scale open source projects (templates or otherwise) available using Babel 7 and Webpack 4. Actually, Babel 7 is still not officially released yet, so there really aren't many even now. If the down-votes were because you think the comment is unrelated to the source article, well... I don't know precisely how to respond to that critique. However, the article (and this discussion) is regarding the underlying principles of React and the linked project is a practical implementation of React (and the underlying principles). I've specifically added a new root level comment rather than piggy-backing off other unrelated comments, which is unfortunately commonly seen on HN. Is the sharing of related (non-competing) open source projects seen as poor etiquette?
- blowski 9y agoI didn't downvote, but... your comment does feel a bit spammy. If you had something to say about why you feel some part of the original post is unclear, and how your link helps to make it clearer, then it would feel more constructive. As it is, it just feels like "This post is about React, so here's my project that is also about React." So I can see why it's getting downvoted.
- meesterdude 9y agoThis was insightful to read, I have often wondered what the underlying thinking was with React. I also disagree with it, but... important to know the thinking for sure. Also helps explain why it's been such a struggle and has been less than obvious to me. I look at react, and I see... shit. As an aside, I'm taking a deep dive reading u on the nuances of JS, so I'm reading along here and I get whats going on at a technical level with the JS; but the actual react code... does not jive with me. Remember when we though SOAP was cool? React kinda feels like that to me. I don't think it really represents a way forward in programming. But you know - I respect that there might be people who totally jive with react, who's brains work differently from mine and see nothing but awesome. This also makes me so, so thankful that I am a Rails developer. React is surely good for certain things, but developer happiness and productivity i think are not among them.
- eropple 9y agoWhy do you "disagree with" the idea of functional projection of application state into views? Because that's all React...is. And, as a Ruby developer going to React, I overwhelmingly disagree with regards to both developer happiness and productivity; I write better, more testable code, faster, when building out a React frontend than I have in any other system I've ever used, bar none.
- meesterdude 9y agowhy did you put 'disagree with' in quotes? I don't think its an idea that accurately encapsulates what a UI is. I'm not saying thats not what drives reacts philosophy... I just think there's more to it. If we're talking about first principles, I think that would a little blunt of a perspective.
- Vinnl 9y agoI think the quotes were because they... Quoted you. Anyway, your comments don't really add anything unless you share what you think is an accurate representation of UI - otherwise, there's nothing we can learn from it, other than that you disagree with the design of React.
- kylestlb 9y agoIt's funny that memoization is some conceptual model for react but that's what compilers have been doing for ever and ever.
- spicyj 9y agoCan you elaborate?
- icc97 9y agoMemoization is a good thing, but not many people understand compliers. So we should celebrate that React is helping to push it into the consciousness of front end developers. React isn't really inventing anything fundamentally new in terms of computer science but I think they are introducing a lot of people to good concepts that already existed. Douglas Crockford was writing about it for JS [0] back in 2008 which is still a long way behind compilers and, say, Haskell but it has been used in JavaScript at least a decade. [0]: https://stackoverflow.com/questions/3798858/explanation-on-javascript-the-good-parts-example-section-4-15 https://stackoverflow.com/questions/3798858/explanation-on-j...
- kace91 9y ago>Most UIs are some form of lists that then produce multiple different values for each item in the list. This creates a natural hierarchy. I find this idea a little controversial - it is certainly true for websites, but I don't think it's necessarily the case for single page applications that have a purpose beyond showing data. I think in those cases the 'natural hierarchy' approach tends to break and the idea of passing arguments in a hierarchical manner can become cumbersome. At least that is my experience so far,
- swyx 9y agoProp drilling was a React pain point for sure but they have solved it with the concept of "context", which was formally released with 16.3. You can also regard this as "implicit props", or "implicitly passing arguments by nature of the hierarchy"
- icc97 9y agofunction FancyUserBox(user) { return { borderStyle: '1px solid blue' ... Perhaps it's just me being pedantic and these are just examples. But when I see React examples that set style properties directly it makes me cringe, like it's ok to go back to a time before CSS just because everything's in JSX.
- WorkLifeBalance 9y agoCSS doesn't work, it's a failed model. It's based off the premise that content and styling are independent. It works very well when that is true. Often they are not. If I'm designing a "date-picker" component, it will be completely broken without the corresponding styling. There can be no separation of content and style, the content does not make sense without the styling to produce the actual final output. Such components require style definitions to function.
- icc97 9y agoThat doesn't make much sense to me. React still just outputs HTML so there's no difference in terms of styling. You're the first person I've heard wanting to scrap CSS and go back to style tags. Sure people prefer LESS/SASS but having styling in a different file and not mixed into JSX code makes style changes simpler for the way I work.
- dmitriid 9y agoNo. People want to have their components styled without the fear of breaking them with an external style. Hence CSS-in-JS etc. There are two ways to look at your code: https://i2.wp.com/pbs.twimg.com/media/DCXJ_tjXoAAoBbu.jpg?w=840&ssl=1 https://i2.wp.com/pbs.twimg.com/media/DCXJ_tjXoAAoBbu.jpg?w=... React mostly makes you think in terms of components. Also: React doesn't output HTML.
- icc97 9y agoSure CSS in JS if you want. But scrapping CSS for style tags is a bad idea. React renders to the DOM which outputs HTML. It's still HTML that can be styled with CSS independently of React.
- sandGorgon 9y agoDan Abramov of the CRA and React team posted a "diagram of modern React lifecycle methods. " here - https://twitter.com/dan_abramov/status/981712092611989509 https://twitter.com/dan_abramov/status/981712092611989509
- danabramov 9y agoThe first time I read this I was pretty confused so here’s some annotations. https://github.com/reactjs/react-basic/pull/7 https://github.com/reactjs/react-basic/pull/7