redux-xstate-poc
vue-svelte-size-analysis
Our great sponsors
redux-xstate-poc | vue-svelte-size-analysis | |
---|---|---|
6 | 18 | |
89 | 300 | |
- | - | |
2.6 | 0.0 | |
over 2 years ago | over 1 year ago | |
TypeScript | JavaScript | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
redux-xstate-poc
-
JavaScript State Machines and Statecharts
Very doable, but not the most ideal syntax, since `createSlice` is focused on "here's an action / thing that happened, here's the reducer that handles that".
On the flip side, you can also use XState state machines as Redux reducers. A state machine is, after all, a function that takes a current state value + some event, and returns a new state.... exactly the same as a reducer function!
David and I have been saying for a while that we'd like to have a more official integration between XState and Redux. A while back, Matt Pocock put together an proof of concept for what a `createXStateSlice` might look like [1]. I actually sat down with David a couple weeks ago and we did some further design discussions about the possibility of using the `@xstate/fsm` package (a smaller version of XState's logic) as a starting point, and generating RTK actions based on that. No code yet, but it seems feasible.
[0] https://dev.to/davidkpiano/redux-is-half-of-a-pattern-1-2-1h...
[1] https://github.com/mattpocock/redux-xstate-poc
-
The new wave of React state management
Fun fact: one of the XState devs did a proof-of-concept showing how to use XState state machines as Redux reducers and integrate the side effects handling as a middleware:
https://github.com/mattpocock/redux-xstate-poc
We'd like to work together to turn that into a more official integration sometime soon.
- Writing React components with State Machines.
-
What does a large XState / Robot3 / FSM-based application architecture look like?
One of the XState devs recently posted https://github.com/mattpocock/redux-xstate-poc , an example of how you can integrate XState into a Redux app for use as a Redux slice reducer + side effects middleware
- @xstate/redux: Official proposal for an XState middleware for Redux
vue-svelte-size-analysis
- What things sveltekit offer better than other javascript frameworks?
- The State of JS 2022
-
A React Developer's First Take on Solid
but that's not true. see https://krausest.github.io/js-framework-benchmark/current.html. There is also a break-even point in bundle size where svelte gets larger compared to vue. see https://github.com/yyx990803/vue-svelte-size-analysis
-
What's next on your JavaScript framework radar for 2023? (Front End)
i did not ignore it. You can read about it here. There is break-even point where svelte falls off compared to vue as the application grows.
- Anyone know what these recent massive spikes in svelte & vue usage are from?
-
The new wave of React state management
The first version of React was released on 2013, it took almost 10 years for Suspense to exist (we _just_ got it now with React 18), that's what I'm talking about. Even functional components and hooks took a lot of time from them get and implement the idea after they tried to use ES classes and made everything much harder to manage. Context also isn't perfect, I like it but the redraw performance is not amazing and doesn't scale at all to bigger applications.
> https://github.com/yyx990803/vue-svelte-size-analysis
This is an interesting comparison I haven't seen before, I wonder if it's true for a complete application using some lib for state management, routing, etc. and if this isn't just a kind of cherry picked example. Thanks for showing this though.
-
All you need to know about the state of Vue.js in 2022
probably only true for small projects
- Solid.js feels like what I always wanted React to be
-
Memoirs of a lone JavaScript developer PART 2 : Svelte. An awful implementation of an old idea.
You are citing this: https://github.com/yyx990803/vue-svelte-size-analysis
-
JavaScript Framework TodoMVC Size Comparison
There isn't only the size of the runtime but the size of the component code. Not all components are equal. Templates in each framework compile differently. Evan You, creator of Vue put together a comparison between Svelte and Vue which was pretty illuminating.
What are some alternatives?
yieldmachine - Components for State Machines, using Generator Functions
pinia - 🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
devtools - Replay.io DevTools
realworld - SvelteKit implementation of the RealWorld app
vuex - 🗃️ Centralized State Management for Vue.js.
vue-native-core - Vue Native is a framework to build cross platform native mobile apps using JavaScript
Dn-FamiTra
rfcs - RFCs for XState and Stately tools
qwik - Instant-loading web apps, without effort
redux-easy-mode - A very easy to understand and use set of tools for Redux. Includes action builders, reducer builders, side-effect middleware, and async actions.
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.