Overall I'm going to say "no". There's no fundamental reason why the front-end should be any more complicated than the back-end. It's all a matter of tools and structuring.
A few caveats however. Modern front-end has to deal with a lot of device compatibility, which is a different requirement than most backend coding has. It requires a different kind of pipeline and a different testing strategy. If you attempt to adapt one workflow to fit both front-and-backend this aspect will become a problem.
The second caveat is perhaps workforce. Front-end has become easy enough that you have a lot of non-programmers contributing there. This is great, but it means you have a higher burden teaching and spreading proper practice on the team.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Overall I'm going to say "no". There's no fundamental reason why the front-end should be any more complicated than the back-end. It's all a matter of tools and structuring.
A few caveats however. Modern front-end has to deal with a lot of device compatibility, which is a different requirement than most backend coding has. It requires a different kind of pipeline and a different testing strategy. If you attempt to adapt one workflow to fit both front-and-backend this aspect will become a problem.
The second caveat is perhaps workforce. Front-end has become easy enough that you have a lot of non-programmers contributing there. This is great, but it means you have a higher burden teaching and spreading proper practice on the team.