But you (almost certainly) started using those backend frameworks after you had experience. You learned the basics first, and then incorporated frameworks when you got to larger projects.

I came here to say the same thing as the original reply in this thread, albeit with slightly different justification:

If you don't know the basics, and can't build a functional site with just HTML/CSS/JavaScript, all of the frameworks will be a nightmare. You should really learn those first, even if it means building a practice site, or completely rebuilding your frontend when you decide to use a framework.

The frameworks can make your life easier, but there's a learning curve, and a huge cognitive burden especially when you are just starting. You'll fight them more than work with them at the start.

That all said, never use what's "hip" on the frontend. JS frameworks typically have the lifespan of a house fly. React is one of very, very few that has remained popular, and continued to get updates for a long time (at least in JS framework terms). It's a solid choice with a huge community, good docs, good tooling, etc. There may be other valid choices, but seriously - avoid anything new and flashy, because that usually just means its deficiencies haven't been found yet, and as soon as they are, there will be a new framework.

I don't know what you're looking for, and what your "not super simple" is, but baseline browser tech provides various controls, layout mechanisms, styling, interactivity, etc.

Do you have a concrete idea of what and where specifically you hope for gains by using frameworks? Do you plan to hold a lot of state on the client that needs state separated from the DOM and its mechanisms? Do you want a standard library of styled components instead of using the native ones or styling them yourself? Do you want more robust JavaScript? Those are all very different concerns and requirements.

I like the low complexity, low barrier, low requirements of baseline web tech. The native html form controls may arguably look "ugly", but those can be styled, individually or through a style-only CSS lib.

Well there is no silver bullet. My two cents is React, but that drives people nuts. Pick one of the big three (React, Angular, and Vue) and then start practicing.

As a frontend dev working my way to the backend, I would probably say a stack of React/Vue, Typescript, and SASS. These are industry standards (or at least, as standard as you can get with such a fractured ecosystem). And/or: learning the ins and outs of an ecommerce platform for theme development, like Shopify or BigCommerce. In terms of frameworks, I prefer Vue because it's a little higher level than React and translated well from vanilla JS.

What’s your goal?

I think building something with what you know should be a good start. Then look into the different frameworks and determine which is the best for your use case to convert it. Definitely overkill.

All that to say, just jump in and pick one.

The most future proof web tech is not using frameworks and libraries at all.

Render native HTML controls.

I also assume it's lower barrier than any of the libs and frameworks you could use, which is always a subset of web tech with the addition of their own concepts.

The general play is:

1. Make non-shit software
2. ???
3. $$$

Web components exist.

What's "complicated stuff"? Your business logic will probably be complicated regardless of what you use. A framework will just add a few more layers of complexity and introduce a (usually fragile) build process.

Idk what you're trying to build, but from this:

I “just” want to build a pretty standard, responsive, modern-looking UI. Ideally without too much boilerplate,

It doesn't sound like you need a framework. Want responsive? Learn how to use flexbox. Want a "modern" look? Learn design, or find some CSS templates to start from.

If you're trying to make a SPA (which a lot of beginners/insane people seem to think is a good default, which it definitely is not), then a framework might make it easier, or it might not. It depends on what you're building. You may be able to use HTMX with a light sprinkling of JavaScript, or may need a full-blown batteries-included framework.

So. What are you building?