Article copied from https://dev.to/fkrasnowski/immer-vs-ramda-two-approaches-towards-writing-redux-reducers-3fe0

Reducers - a core element of Redux's philosophy that tightly grabs mutations of a given state in one place. In theory, the pure nature of reducers should lead to great scalability, readability, and make us all fortunate children of Redux god. But even the brightest idea can be dimmed if thrown on the one most pediculous soil...

Yes. I speak about JavaScript. Writing complex pure functions in vanilla JavaScript is harsh. Avoiding mutations is extraordinarily hard. Matching against actions? There are no Variants/Enums in JS, you have to use strings instead. And you land with a poor switch statement taken straight from the hell. Regardless, Redux is the most popular state manager for React applications

## The path to purity
Consider the two ways to make your life easier, the first one will be the Immer - Immer is a package that lets you deliver the next state by "mutating" the draft of the previous state:


Two approaches towards writing Redux reducers

Immer vs Ramda -

Article copied from https://dev.to/asayerio_techblog/is-redux-dead-1d2a

React revolutionized front end development as most people knew it when it was first released. This new approach to writing code triggered incredible innovation in how to handle state changes and UI updates.

This revolution had its downsides, too. One of them was a culture of over-engineering solutions to challenges that could be solved in simpler ways. A typical example of this is how state has been managed in React applications.

Redux has become a hallmark of many React applications created in the last couple of years. The allure of having a single state object, available everywhere in your application sure sounds nice. But has its time passed? Has React evolved to a point where these kinds of state management tools add more complexity than they solve?

This article aims to give you a deeper understanding of which situations warrants state management tools like Redux. We’ll discuss the reasons behind the rise of Redux, and what has changed in the last couple of years - both in React and in Redux. Finally, we’ll look into what might be coming in the future.

## Redux - and why people started using it
When it was first released , React didn’t have an officially supported way to pass data far down the component tree. If you had some kind of shared state, configuration or other information you would like to use anywhere in you application, you had to pass it down from parent to child to sibling to another child. There was a way to avoid it, but that way - the “legacy context API” was never officially supported, and was documented with a warning that it should not be used.

About the same time React was released to the public, some other Facebook engineers introduced a blueprint for how they created front end applications - the Flux architecture. It complimented React’s component-centric design by having a unidirectional data flow, which made things both easy to follow and simple to understand.

```js
const rehypePrism = require('@mapbox/rehype-prism')
module.exports = {
  module: {
    // ...
    rules: [
      // ...
      {
        test: /.mdx?$/,
        use: [
          'babel-loader',
          {
            resolve: '@mdx-js/loader',
            options: {
              rehypePlugins: [rehypePrism]
            }
          }
        ]
      }
    ]
  }
}
```


Context, hooks, and why it solved much of what Redux did

Is Redux really Dead?

Article copied from [https://dev.to/renaissanceengineer/7-unique-apis-for-your-next-project-4hf9](https://dev.to/renaissanceengineer/7-unique-apis-for-your-next-project-4hf9)

Whether you just want something to help you get a job or create a side project that earns you some money, all of these APIs are valuable.

I'll be putting out a video soon with more in-depth project ideas so be sure to subscribe if you're interested in seeing that

1. Shodan API
You can think of Shodan as Google for every device connected to the internet. They crawl the web and catalog devices. You can sign up for a developer account and programmatically access their data and filter based on numerous factors. Some things people have found exposed and unsecured on Shodan:

* A French hydroelectric plant control system
* entire cities transportation grids
* databases
* industrial freezers with 10's of thousands of dollars in goods
* car washes that can be remotely shut down

With Shodan you are really only limited by your imagination, just make sure you don't get yourself arrested.

## Conclusion
If you think I forget any APIs let me know. Also I'd love to see people brainstorming cool ideas in the comments below.


Need some inspiration for a new project? In this article I'll go over what I think are 7 of the coolest APIs around that make it quick and easy to build impressive projects.7ap

Immer vs Ramda -

Is Redux really Dead?

7 Unique APIs for your next project