I've read the docs including the docs Componentisation vs inheritance, however I completely disagree, sure they say they use it on facebook and have never had the need for inheritance, but we are talking about facebook, where the interface is so ridiculously simple, no you more then likely wouldn't need inheritance. Inheritance is such a powerful tool and it can be used simultaneously with componentisation, which from years of experience with react makes it even more powerful. I'm not going to bother going into specific use cases, I have better things to do. but if the developers of react can't foresee that other developers are trying to build things that they could not even begin to comprehend was possible with their own framework, then this framework is doomed. this frame work in ye old days was great, it took care of the piddly crap that most developers couldn't be bothered with, but beyond that stayed out of the way. And it was fantastic, in-fact its a great shame that more frameworks don't follow the same model.
Unfortunately react is now starting to reach the point of dictating how I should code, and hence if it continues down this path it will get in my way, and when that day comes I'd sooner ditch react, either find another framework that does what I want, or build my own.
as for class components I prefer using classes because I think that it is the best way to adhere to the first and most important rule of coding, keeping code structured and readable, and yes for the same reason I loath the absolute overuse of arrow notation!!!!
Top comments (0)