Things I wish I knew about state management when I started writing React apps

Post by veeralpatel979 » Tue, Feb 11, 2020, 11:34 PM UTC

jaimex2 wrote: post #251

Been using alt.js for ages and continued to make use of it in React, never really ran into the issues described. Use it as a store or cache that alerts all your components of data changes, works well enough.

Post by UberMouse » Wed, Feb 12, 2020, 2:16 AM UTC

adamkl wrote: post #186

UberMouse wrote: post #121

Earlier quoted context omitted.

> e.g. having the “NavigationService” change which links should be available by listening to a state change on the “UserSession” service as a user becomes authenticated. Could you expand on how you're achieving this? I'm creating a new project using xState at work and this is one of the things I've been trying to come up with a solution too. My biggest problem is the pattern I've set up for routing on top of xState (…

We keep things very simple. Maybe that will have to change as the code base grows, but for now it works and it easy to grok. On start of the application we create singletons of our state machine backed services, and manage the dependencies between them manually. That is, we create an instance of the UserSessionService and then pass it into a "constructor" for the NavService. That constructing function creates the Nav…

Post by FpUser » Wed, Feb 12, 2020, 2:54 AM UTC

k__ wrote: post #311

FpUser wrote: post #308

Earlier quoted context omitted.

Delphi and it's opensource cousin Lazarus/Freepascal are doing just fine and I use those to implement desktop applications. Single exe with no dependencies. Beauty. Sure they're not popular in North America but I could care less. Those tools save me a boatload of time. There is also QT. "The answers were: These tools were good for one developer or small teams, but textual dev tools scaled better to big teams." Utter…

How big is your team?

Post by nohuhu » Wed, Feb 12, 2020, 6:23 PM UTC

the_gastropod wrote: post #313

dragonwriter wrote: post #312

Earlier quoted context omitted.

> The ~100ms between submitting a form and getting error messages isn't that big of a hurdle, in my experience Sure, it's the >100ms between the user entering the first value that might have an error and the user submitting the form that's a much bigger problem between validate-on-server-on-submit and validate-on-client-on-entry. > But I don't agree React _benefits_ developer productivity. On the contrary, I think it…

I've been professionally working on SPAs for the past 7 years. I'm familiar. I strongly disagree with the premise that it's in any way more productive. I'm, at a minimum, 2x more productive building something the traditional "Rails way" with server-rendered HTML, and a handful of JS enhancements where necessary vs doing a full-blown SPA. I'd love to do a showdown, and challenge anyone to a head-to-head non-trivial ap…

Post by PaulDavisThe1st » Thu, Feb 13, 2020, 12:08 AM UTC

hippich wrote: post #284

PaulDavisThe1st wrote: post #275

Earlier quoted context omitted.

I just thought of another critical difference when using "Qt, etc". These toolkits all have at their heart an event loop that looks something like: while (!should_quit()) { wait_for_user_input_or_other_events(); process_events(); // may mark some components for redraw redraw_anything_that_needs_it(); } So if user input or some data source indicates that some on-screen component now needs to be red with a yellow borde…

It is pretty much the same, except there is no explicit loop and calls to wait for events written in JS/React code. Javascript itself runs a loop, instead of polling for events, you define events handlers, and DOM/React handles "redraw anything that needs it" part.

   Gtk::Main app;
   ...
   app.run ();