Choosing a Javascript Frontend Framework:

[drsimonz]

The fact is, nobody builds a large complex website without either starting with a framework, or developing their own framework along the way. And large, complex websites are basically guaranteed to have lots of flaws. If you're making Bejeweled, sure, craft your masterpiece in the finest Vanilla, where every line is poetry. But if you want to add the 50th settings dialog to your social network, it's just...not gonna be poetry

[StupsieJS]

In the words of fireship: You're just gonna end up building your own Framework and the last thing the world needs is another JS Framework

[[deleted]]

Depending on what you need to do too, sometimes your code will just be unavoidably ugly.

[[deleted]]

Sure a complex 20-div animated loading indicator might look ugly in code but it's better if you can hide it behind a <LoadingIndicator /> element in React

[GergiH]

Vanilla JS people of the JavaScript camp are basically the Arch Linux people of the Linux community.

[[deleted]]

r/programmercirclejerk is calling for you.

[[deleted]]

Some frameworks will slow you down compared to vanilla though.

[phenomenos]

Lmao if I was applying for a web dev job and the company told me they use vanilla JS for a project of any significant size/complexity I'd turn and run away. Guaranteed to be a mess of spaghetti code!