9
13 Comments

Why do you prefer React?

This is a serious question. I'm an experienced developer and I prefer Vue due to its elegance, small bundle size, and most importantly, high performance.

React seems to be more dominant though and I can't figure out why.

Also, does no one want to author CSS any more?

I feel like I'm the only one not using React or Tailwind and I want to see someone else's point of view.

Thanks!

  1. 4

    React has something like 4.5:1 weekly downloads compared to Vue. More people using React means there is greater ecosystem of supporting libraries. Of course I am sure you can make a React component work inside of Vue (using Vuera for example) - but why add extra complexity? More importantly, there are more React developers to hire if your building a company and personally I like that FB supports it - gives me confidence it will continue to be evolved and pushed forward.

    Don't see Vue as compelling enough to bother with.

    1. 2

      This comment was deleted 2 years ago.

  2. 3

    I like React's functional style more. I used Vue as well and I hated the template languages present in Vue, Svelte, Angular etc. Only React seemed to be the sane one with using plain JS/TS to loop over items, use conditionals, etc.

    TypeScript support is way better in React than Vue and others due to this fact of using only pure JS to render the screen.

  3. 2

    I had to make this choice a few months ago. I already knew the vanilla stuff (html/js/css) but had very little experience with frontend frameworks.

    After some research, i chose React and here's why:

    • Vue introduces a whole lot of new concepts, so the barrier to get started seems high.
    • React has few basic concepts and you can jump right in, without knowing much about it. You can explore more complex concepts as you progress.
    • Community support. A lot more articles and tutorials around React.

    Because of the lower barrier to get started, React has more people. Because it has a bigger community, it has more educational material... and the cycle continues.

    1. 1

      This is new for me. I know both and I find Vue much easier to get started.

  4. 2

    TBH I even prefer Svelte over Vue for the same reasons. But I guess it's the curse of popularity. Not all things popular are great - but they do usually allow for a bigger audience. You see the same thing in the music industry.

    Looking at it from a business angle though, it means it might be cheaper to go with popular - at least at first. More candidates, more resources and more ready-to-use components to chose from.
    Whether this still proofs to be the best choice in the long run is not as easy to answer - and surely up for debate. But that's a bit beyond the scope here I guess.

  5. 1

    I don't prefer react. I prefer Vue.
    And I don't use Tailwind.
    I use Quasar framework.
    I am super happy with it, even in large applications.

  6. 1

    Where is the best react community? ( like forums and such ..)

  7. 1

    Vue doesn’t have adequate Typescript support or enterprise features. It also feels behind compared to React and has a much smaller community and ecosystem. Those are my main thoughts after learning and using both.

    I personally like TailwindCSS because it makes implementing custom designs far easier. For dashboards, I usually use Material UI.

    But, the best framework to use is the one you already know or the one you are paid to use

  8. 1

    I like React because it is Javascript all the way down. JSX is just Javascript expressions and Javascript objects. I find the design - especially hooks - elegant and consistent.

    I found Vue difficult to pick up because of the template language. I picked up React in half a day.

    Two other huge positives - 1) You can easily transfer the knowledge to React Native 2) It's backed by Facebook.

  9. 1

    I learned it a long time ago and don't want to learn another framework because I want to focus on the product. All frameworks have problems, most are subtle and hidden.

    The other day I was on the Google DialogFlow website to delete some agents I created more than a year ago because Google Cloud would not allow me to delete projects with agents hanging. The website didn't even show the agents exited. Plus the site is so buggy.

    Somehow it's costly even for Google to maintain an interface, probably in Angular.

    Feels like the whole JS ecosystem is just overblown.

  10. 1

    My sole motivation for learning programming was to launch MVPs, so it was a real no-brainer for me when I learned about React Native.

    "You're telling me I can learn one framework instead of one framework for web and two totally different languages for mobile???"

    All that stuff about scaling and efficiency are concerning problems that are much better to have than the "Nobody uses my thing" problem. Therefore, I optimize for minimal time spent learning/remembering/brushing up on technical knowledge. All I need it to do is what I want it to do.

    Same reason I went with Node.

  11. 1

    I can give my .02 on this as a Developer as well.

    Im mainly an angular / c# or nodejs Dev.

    When I was first getting started in front end work years ago react was definitely quicker and easier to get up and going because it was inherently less structured. Which is great and absolutely wonderful when youre small as it gave you a bunch of freedom to write things with a preference for speed and less 'structure'. Start ups often need to ship something yesterday.

    Having worked at numerous start ups and bigger corporate jobs I can speak to the otherside of this too.

    Because react is more 'flexible', as your engineering team inevitably grows you will hire teammates who all have their own flavor of how they like to write and structure their react code and components.

    This variety can be quite burdensome for larger teams.

    On the Angular side of things, I found that it took way more effort initially to get things up and going because of the structures involved. BUT as the team grew there was more 'sameness' largely speaking across the code being written when it came to bigger teams.

    This obviously doesnt mean you cant write shitty unstructured Angular or cohesive uniform react code.

    This has just largely been my experience having worked with both frameworks in both start ups and corporate settings.

    1. 1

      This was my exact experience, too. The Angular codebase at my employer is a 1,000+ component, service, and state solution that is shared between 4 products. Following the same set of organizational standards has allowed us to have a straight forward and repeatable way of solving problems.

      In our experience, it can still be difficult to onboard new developers just because over the years we've developed our own set of best practices in the way that we organize and do things.

      Angular is definitely more opinionated and structured than React, and that can be a good thing as you grow, but I would say the single most important thing is to have a set of standards that everyone agrees on. If developers disagree with standards, talk about them and evolve the standard as you go.

      The reason I personally prefer React is because I feel more expressive when working with it than I do Angular. It's easier to bring in cool libraries that I find online to use and the ecosystem is so much more vibrant. A lot of it comes down to personal preference, but I also dislike how Angular breaks html/ts/styles out into separate files. The module system is helpful, but can seem like a lot of overhead and confusion.

Trending on Indie Hackers
After 10M+ Views, 13k+ Upvotes: The Reddit Strategy That Worked for Me! 42 comments Getting first 908 Paid Signups by Spending $353 ONLY. 24 comments 🔥Roast my one-man design agency website 21 comments I talked to 8 SaaS founders, these are the most common SaaS tools they use 19 comments What are your cold outreach conversion rates? Top 3 Metrics And Benchmarks To Track 19 comments Hero Section Copywriting Framework that Converts 3x 12 comments