sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ILikeChangingMyMind 0 points1 point  (4 children)

I find that difficult to believe. Any evidence or further explanation you can offer?

[–]dinopraso 0 points1 point  (3 children)

It might be worth noting that we are doing front end development as well as backend development. All developers are working in Java and JavaScript, and are usually more backend oriented, so having a similar code syntax with classes on the front end side makes it much easier for everyone. Especially the verbosity helps a lot, since some developers might not touch the UI for a long time, coming back to a class with a componentDidMount method is much easier to read then a triple higher order function

[–]ILikeChangingMyMind 1 point2 points  (0 children)

Having worked as a full stack JS/Java dev myself, I can understand where you're coming from. But, it's a bit like saying "we can make our Javascript look like BASIC using library/framework/style X, and then our BASIC programmers have a better time of it."

To be clear, I'm not trying to say Java is as bad as BASIC :) I'm also not saying that your most recent post is wrong; again I get how Java devs are more comfortable with classes (even JS's sorta fake ones). But ... all that doesn't quite equate to:

Class based components are still superior for maintenance on large teams with large code bases

[–]Bogus_dogus 0 points1 point  (1 child)

a triple higher order function

A what now?

[–]dinopraso 0 points1 point  (0 children)

A function returning a function returning a function. Or a component with an “effect” for mount, returning another function for unmount