DEV Community

Discussion on: Clean Architecture on Frontend

Collapse
 
giovannicorrea profile image
Giovanni Correa • Edited

This is one of the most comprehensive and well-written posts I've ever read. The subject is also quite crucial. I'm not sure why the front end world (in general) doesn't seem to care about architecture or things like SoC or DI. More people will comprehend the importance and relevance of these strategies if we can share them more widely.

The main reason for using clean architecture (for example, Co2 Cartridges uk) in frontend projects, in my opinion, is to be able to swap out UI libraries with minimal effort. We lose this capability by relying on React for non-UI layers.

Collapse
 
bespoyasov profile image
Alex Bespoyasov

Thank you!

Totally. I had some hard time working with coupled “React-driven-code”, it was difficult and inefficient.

I now tend to less depend on third-party code and modules and decouple my own code from the “outside” one.

Collapse
 
danko56666 profile image
Daniel Ko • Edited

This might be a controversial opinion, but I think it's because of React, not frontend (but not 100% because of it, just one of the big reasons).

For one, a lot of the frontend devs now, they only know React but aside from that, the concept of React is to couple things to hell. Just look at how components are built in React. They have the logic and the UI together. Yes, you can split them up and do stuff like this clean architecture, but at that point...why are you using React really?

It's a question I had in the back of my mind for a long time.