Yes, I think you would need a good immutable collection library to make Redux work well from Java. In our application we are just using React State. This works fine because we are replacing relatively small isolated parts of our application currently (1 or 2 connected screens at the most). Even Facebook uses this approach for large parts of their application. If you were building a complete application or replacing a major module, it may be better to look at a state manager. I think either Redux or MobX would work or you could roll your own in Java.
On Monday, May 1, 2017 at 1:02:32 PM UTC-4, Ivan Markov wrote: > > Side question: I can imagine that the lack of object spread probably makes > Redux a bit annoying to use from Java. Yet, if you are not using neither > Redux nor MobX, how are you managing your state? > > > On Monday, May 1, 2017 at 3:48:51 PM UTC+3, Paul Stockley wrote: >> >> I agree both Redux and MobX are both pretty stable. The decision was more >> a reflection on the current state of the GTWReact projects. I would say >> both are really proof of concepts at this stage. Redux in particular would >> really need interfaces building to the common middleware to be really >> useful. >> >> On Sunday, April 30, 2017 at 11:05:08 AM UTC-4, Mark Erikson wrote: >>> >>> For what it's worth, as a Redux maintainer I can assure you that Redux >>> is very stable and not going to meaningfully change (at least at the API >>> level) from here on out :) >>> >>> On Sunday, April 30, 2017 at 8:27:10 AM UTC-4, Paul Stockley wrote: >>>> >>>> I have just released a new version of the GWTReact >>>> <https://github.com/GWTReact> projects to support GWT 2.8.1 >>>> >>>> As of this release, I will no longer be maintaining the MobX and Redux >>>> projects. Our company is not using them currently and I don't have the >>>> time >>>> to keep them updated. In the future, we may update MobX if we start using >>>> it in production. If you would like take over maintenance of either of >>>> these projects please let me know. >>>> >>>> *Road Map* >>>> >>>> With the current release, I feel pretty good about the quality of the >>>> projects. We are starting to use both gwt-interop-utils and gwt-react in >>>> our production code with excellent results. However, I think to get to a >>>> 1.0 release I need to make the following changes: >>>> >>>> >>>> 1. Migrate gwt-interop-utils to use the new GWT base project >>>> 2. Migrate gwt-react to use elemental 2 >>>> >>>> I will start working on these objectives in a month or two. The main >>>> determining factor on how quick this happens will be how fast elemental 2 >>>> matures. >>>> >>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
