• act
  • 1. Examples
  • 2. Goals & principles
  • 3. Cheat Sheet
  • 4. Comparisons
    • 4.1. For React developers
      • 4.1.1. JSX vs JSON
      • 4.1.2. Class and id shortcuts
      • 4.1.3. JS vs HTML attribute names
      • 4.1.4. class-names vs class-lists
      • 4.1.5. Lifecycle events
      • 4.1.6. shouldComponentUpdate vs memoization
      • 4.1.7. Events
      • 4.1.8. Subscriptions
      • 4.1.9. Testing
      • 4.1.10. Reselect vs Ramda
    • 4.2. For Elm developers
      • 4.2.1. update vs reducer
      • 4.2.2. Html helpers vs JSON
      • 4.2.3. Actions
  • 5. Concepts
    • 5.1. Using JSON for rendering
    • 5.2. Unidirectional data flow
    • 5.3. Single model & reducer
    • 5.4. Reducers
    • 5.5. Actions
    • 5.6. Signals: sources & processes
    • 5.7. History
    • 5.8. Subscriptions
    • 5.9. Storage
    • 5.10. Memoization
    • 5.11. Presenters
  • 6. API
    • 6.1. main
    • 6.2. processes
    • 6.3. signals
    • 6.4. nest
    • 6.5. combine
    • 6.6. storages
    • 6.7. subscriptions
    • 6.8. actions
    • 6.9. testHelpers
  • 7. Real world
    • 7.1. Nesting
    • 7.2. Testing
    • 7.3. Performance
    • 7.4. Errors & debugging
    • 7.5. Webpack tips
  • 8. Wanna help?
  • Published with GitBook

Hello Act

For React developers

Here's a selection of things in which Act departs from React.

  • JSX vs JSON
  • Class and id shortcuts
  • JS vs HTML attribute names
  • class-names vs class-lists
  • Lifecycle events
  • shouldComponentUpdate vs memoization
  • Events
  • Subscriptions
  • Testing
  • Reselect vs Ramda