This is a weekly roundup of awesome DEV comments that you may have missed. You are welcome and encouraged to boost posts and comments yourself using the #bestofdev tag.
@slavcoder added a hilarious comic in response to How do you come up with new side projects?:
Be careful with side projects :)
@markerikson shared an informative and thorough reply, addressing the question: Should I use Redux?:
Hi, I'm a Redux maintainer.
I can assure you that Redux is not "deprecated", "dead", or "dying". Also, while Context is useful, it is not a replacement for Redux.
Redux will continue to be very relevant and useful for a long time. It's currently used by 50% of React apps, and lots of folks are continuing to learn it on a daily basis.
I covered this and a number of reasons to use Redux in my Reactathon 2019 talk on "The State of Redux", and my post Redux - Not Dead Yet!.
TL;DR:
- Consistent architectural patterns
- Debugging capabilities
- Middleware
- Addons and extensibility
- Cross-platform and cross-framework usage
- Depending on your app's setup, much better performance than working with just Context
Related to that, you might also want to read through these resources:
- Dave Ceddia: React Context API vs Redux
- Mike Green: You Might Not Need Redux (But You Canβt Replace It With Hooks)
- Sergey Ryzhov: From Redux to Hooks: A Case Study
- Eric Elliott: Do React Hooks Replace Redux?
- Chris Achard: Can You Replace Redux with React Hooks?
In addition, our new Redux Toolkit package is now our recommended approach for writing Redux logic. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once.
@jdmedlock posted their awesome plant-based π΄ battle station π¦ πͺ Show your COVID19 work from home desk? π©π»βπ»πͺ:
You can't have too many plants.
@radiomorillo offered some great insight in What non-coding skills do you want to learn next?:
Hey Dan! Can I offer some suggestions?
- Write the Docs has a recommended book list for folks interested in learning more about technical writing
- UC San Diego Extension offers a 10-week fully online technical communication course which I found helpful
- Google also created an online technical writing course for engineers which is free
- My personal blog has a lot of posts related to content for developers
Hope this helps! :)
@patricktingen shared their coding origin story in the At what age and in what language did you write your first line of code? thread:
I think I was around 12 years old (~1982) when I wrote my first basic program. On paper. Yes, paper. I got infected with the programming virus by a book of a friend of my parents. They had a commodore 64 with a book that belonged to it, with instructions on how to program in basic. I just loved it and started to write my own program on paper. Later - in school - I programmed on a TRS-80 system and even later I got my own MSX computer. Today I am still programming. And I still love it. Even after almost 40 years.
See you next week for more great comments β
Top comments (2)
You have to find the easily bluescreen of death error code here.
Congrats to @slavcoder , @markerikson , @jdmedlock , @radiomorillo , and @patricktingen for making the list this week!