DEV Community

Discussion on: JavaScript Should Be Your Last Resort

Collapse
 
olpeh profile image
Olavi Haapala

Thanks! Yeah, I agree. But this was based on my current project(s) where React is used, and that won't change in the near future. It's easier to change how you use the framework instead of rewriting everything. Also, it's good to keep in mind the actual impact on the end users.
There are even solutions that use React on the server, but have no runtime JS – so the end users don't get punished for your choice of framework.

Collapse
 
zenwork profile image
Florian Hehlen

I have had to do a lot of React lately. I think there is also some arguments to be made about how much you use it. For example there is a tendency to break everything down into micro components which gets excessive. I think the functional and stateless dogma leads often to heavy to execute and unreadable code.... which is funny because that is exactly what React wants to solve.

Thread Thread
 
olpeh profile image
Olavi Haapala

I think this is also a problem that is not React specific. This problem will occur in every project that grows large enough.

Thread Thread
 
zenwork profile image
Florian Hehlen

For sure! I have seen this in other languages and with all sorts of frameworks over the years. It is very tempting as a developer to look at any DX improvement as an improvement for the universe.