I am a huge fan of Arrow functions. They have changed the way we write code. They have cured the cloudy behaviour of this. They let us define functions without function keyword 😅. This article collates one-liners — written using arrow functions — with their explanations.
tl;dr: I recently updated my Portfolio and applied a lot of performance-related techniques. This is about the technologies that I used to achieve better loading and compression behaviour. T
However in the modern browser fetch should be mostly natively supported. I still see a lot of people rely on libraries like axios, eventhough axios can be nice, why add a dependency to your app when you can just use the native fetch API built into the browser.
A linked list is a data structure that stores multiple values in a linear fashion. Each value in a linked list is contained in its own node, an object that contains the data along with a link to the next node in the list. The link is a pointer to another node object or null if there is no next node.
We’re going to overview evolution of reducers in my Redux/NGRX apps that took place over the last two years. Starting from vanilla switch-case, going to selecting a reducer from an object by key, finally settling with class-based reducers.
So where does that leave us? Are there any fundamental differences between React functions and classes at all? Of course, there are — in the mental model. In this post, I will look at the biggest difference between them. It existed ever since function components were introduced in 2015 but it’s often overlooked: