simple_states
A super-slim statemachine-like support library (by svenfuchs)
state_machines
Adds support for creating state machines for attributes on any Ruby class (by state-machines)
| simple_states | state_machines | |
|---|---|---|
| - | 5 | |
| 95 | 795 | |
| - | 1.0% | |
| 0.0 | 3.3 | |
| almost 7 years ago | 13 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
simple_states
Posts with mentions or reviews of simple_states.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning simple_states yet.
Tracking mentions began in Dec 2020.
state_machines
Posts with mentions or reviews of state_machines.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-21.
- Gem adds support for creating state machines for attributes on any Ruby class
-
Practical State Machinery
State Machines (Ruby) - A popular library providing a Ruby DSL for easily building finite state machines
-
Why Developers Never Use State Machines (2011)
As a regular user of the state_machine Ruby gem, I wouldn't recommend it. If you don't believe me, just check out the "Class definition" section of the usage examples: https://github.com/state-machines/state_machines#usage
The problems are obvious. It's built on magic and indirection. This leads to difficult to debug state machine problems. For anything beyond simple state machines you quickly lose any idea of what your object is doing.
-
ActiveRecord: Adding Boolean methods for DateTime columns
Might this be better handled with a state machine with active record integration?
-
Ruby 3 Released
Here's an example of how it can happen - look at the code examples in https://github.com/state-machines/state_machines - almost everything you are coding is in the DSL of that library if you are using it:
What are some alternatives?
When comparing simple_states and state_machines you can also consider the following projects:
State Machine - Adds support for creating state machines for attributes on any Ruby class
AASM - AASM - State machines for Ruby classes (plain Ruby, ActiveRecord, Mongoid, NoBrainer, Dynamoid)
Statesman - A statesmanlike state machine library.
transitions - State machine extracted from ActiveModel
state_shifter
FiniteMachine - A minimal finite state machine with a straightforward syntax.
simple_states vs State Machine
state_machines vs AASM
simple_states vs AASM
state_machines vs State Machine
simple_states vs Statesman
state_machines vs Statesman
simple_states vs transitions
state_machines vs state_shifter
simple_states vs state_shifter
state_machines vs transitions
simple_states vs FiniteMachine
state_machines vs FiniteMachine