Any examples of good tile-based board games written in React (or other JS frameworks)?
I made a simple chess app with React and RethinkDB: https://github.com/mikemintz/react-rethinkdb/tree/master/exa...
Best practices for building large React applications
21–26 of 26 posts
Re: Best practices for building large React applications
#22Any examples of good tile-based board games written in React (or other JS frameworks)?
An example is chessground [1], the UI for the lichess [2] chess game, written with Mithril [3]. [1] https://github.com/ornicar/chessground [2] http://lichess.org [3] http://mithril.js.org
Thanks & thanks @mikemintz & baddox, this is exactly what I'm looking for.
Re: Best practices for building large React applications
#23Nice insights on the actual usage of React, hopefully I have the time and opportunity to work on it :)
I would like to encourage more people to share on StackBus (FYI, I built it) on why they use React and what they use it for, to provide more insights to those who are evaluating React http://www.stackbus.com/
Re: Best practices for building large React applications
#24Earlier quoted context omitted.
Flux is a way to organize interactions with data and business logic, so that React only has to worry about the UI. Specifically, it breaks down behaviours into functional streams that don't interrupt each otherr.
so what is relay ? is it on top of flux ?
AFAIK (I have not worked with Relay yet) Relay is a data layer, (which currently flux handles already). Relay is component based, as opposed to flux, which handles data in a top-down manner.
As I understand it, when we implement Relay, flux will be relegated to handling UI behaviour and changes. So, React would handle DOM manipulation and rendering, Flux will handle user behaviour and changes to state, and Relay will provide the data.
Re: Best practices for building large React applications
#25Nice insights on the actual usage of React, hopefully I have the time and opportunity to work on it :) I would like to encourage more people to share on StackBus (FYI, I built it) on why they use React and what they use it for, to provide more insights to those who are evaluating React http://www.stackbus.com/
Please don't promote your project repeatedly in threads. It's fine if you have something specific to say about it that naturally forms part of the conversation. But artificially injecting it into conversations isn't ok.
Re: Best practices for building large React applications
#26Nice insights on the actual usage of React, hopefully I have the time and opportunity to work on it :) I would like to encourage more people to share on StackBus (FYI, I built it) on why they use React and what they use it for, to provide more insights to those who are evaluating React http://www.stackbus.com/
Please don't promote your project repeatedly in threads. It's fine if you have something specific to say about it that naturally forms part of the conversation. But artificially injecting it into conversations isn't ok.
Caught, Guilty, Noted, Thanks.