Re:React best practices
by mattmanser on Monday May 03, 2021 @05:49PM
(#27031188)
I've already commented on the GP, but that's not a good thing in my experience in the long run.
Techs that quickly end up with a general "best practice" code style are a lot easier to work with, and a lot, lot, lot, lot easier to maintain.
Clojure and co are a similar vein of favoring small, focused practices and libraries over one-size-fits-all frameworks.
YMMV, but having been on both sides of this equation at companies large and small, I find the library (I.e. react) approach favorable over the framework (I.e. angular or ember) approach.
Re:React best practices
by mattmanser on Monday May 03, 2021 @06:01PM
(#27031347)
That's got nothing to do with my comment though. At all, like whoosh, you've completely missed the point of it.
My point was that it doesn't matter if it's a framework, library, language, configuration, or whatever. If the design of that thing means that the community coalesces around a particular style of usage, it's much better for everyone in the long run.
Case in point I literally only use JSX and ReactDOM.render().
Some would call this a blasphemy. Works great.
One react codebase being different from the next is pretty much the norm. I even doubt that the majority of react developers have fully transitioned from classes to hooks.
I personally wasn't a fan of any advice in this article. But again, it's all just opinion and personal experience. I didn't feel anything covered fell in the area of best practices.