I’m an experienced backend developer. To me, the backend world seems super simple compared to the frontend world.

It seems like there are a million options and I don’t have the experience to say what’s good and what’s not. I’m hit with major choice paralysis, basically.

I don’t have any special requirements - I “just” want to build a pretty standard, responsive, modern-looking UI. Ideally without too much boilerplate, in a framework that “feels good”, in a way that might at some point attract other contributors as well, if I get to the point of open sourcing.

Of course I could just reach for the most popular thing i.e. React, but that doesn’t seem to be the “hip” thing to use nowadays (or maybe I’m wrong? What do I know, I’m a backend dev).

But even if I choose a framework, there’s a million other libraries out there to choose as well. For instance, which UI library to choose? What about observability and state management and authentication and so on?

Sorry if this is a bit ranty. I am honestly just looking for an experienced frontend developer to point me in some direction (i.e. some set of frameworks/libraries; a “stack” if you will), so I can get out of this choice paralysis.

What would be your go-to stack for a new frontend project today?

    • SorteKanin@feddit.dkOP
      link
      fedilink
      arrow-up
      3
      ·
      3 days ago

      I am literally asking for help for that exact thing in this thread. I come here asking “What frameworks should I learn?” and your response is “just pick something yourself”? I mean why are you even writing this comment, this is the most irrelevant and useless response to my question I can imagine.

      • TheV2@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        3 days ago

        Sorry, if it sounded like you should do the work yourself. What I meant is that I’d advise you to not think too much about your first choice and instead pick up any framework just to get started. Just one of the most popular ones as a starting point. Eventually you’ll understand what you like and dislike about that framework and you’ll have a better practical understanding of your own requirements for a front-end framework. The differences are too specific to study and examine them on paper.