Don’t bother learning React JS.

  1. 4

    I feel that whoever wrote this article is either incredibly junior, or absolutely has no idea what he or she is talking about.

    Regardless, I'd highly advise you not to spread completely inaccurate information as you are not helping your self, and certainly not helping others.

  2. 2

    React requires extremely complex build tooling

    Ahh... nonsense. Just like the rest of the article.

  3. 2

    I'd struggle to hire someone on the frontend who couldn't get up and running quickly with React. Knowing HTML+CSS+JS is not the same as understanding how to build a web app quickly and robustly (e.g. lifecycle considerations). There are other frameworks that can do that besides React of course, and that can be a great place to a start discussion in interviews (e.g. someone prefers Ember/Flutter/? and can explain why it would be advantageous to go that route).

    1. 3

      Thanks for saving me time haha

    2. 1

      if the information given in the article wasn't wrong I would be ok with that title... Author clearly doesn't know what React is

    3. 1

      yeah just write something provocative...

  4. 1

    I have read this article and Just provoking article. Main things to learn from it that you must learn basics HTML CSS AND JS

  5. 2

    Reading the comments under this post taught me way more than reading the article tbh. Thanks guys!

  6. 17

    The provokative title isn’t justified in the article beyond the benefits of learning basic JS, CSS and HTML.

  7. 9

    Learn HTML, CSS and JavaScript before learning anything front-end, be it React, Vue or Angular.
    Also, learn React.

    1. 1

      HTML, CSS and Javascript are the foundations of front-end development.

  8. 7

    Really? You are wrong on react's pros and you are even more wrong on reacts cons. You should not write articles about the things you don't know specially if you are aiming beginners! You may cause someone to change their mind looking at all the false information in this article

  9. 6

    Sigh. This is dissapointing. Just because the industry caught up to component based architecture doesn't mean we should stop using React. Show us why something else is better!

  10. 4

    This article reads like one big non sequitur.

  11. 2

    Terrible advice. React should be the default for anyone here. Reason not to use it is you know something else better.

    I laughed at the first reason not to use in that article. “Separation of concerns”. Just build apps that people like. You’ll build faster with html css and js in the same file.

  12. 2

    Quite a stretch imo - good intentions but clearly reading too deep into some of those cons. React doesn't prevent anyone from learning anything - as a matter of fact any React tutorial (beginner) or course I've ever seen ... every React Book I've read the very FIRST chapters are usually 'brushing up your Javscript' or 'getting up to speed with ES6 standards so you can properly implement those principals into your React' at the end of the day React is still JS - so learning React is learning JS, with a twist.

    It does take us away from the separation of concerns that was highly stressed in early days pre CSS3 / HTML5 mostly - in xHTML days we just rolled with it then the separation of concerns really became industry standard with the roll out of responsive web design.... but with the web maturing - now it happens to have one framework, sorry - Library, rather that teaches jsx which is losing touch of the SOC but gaining the component mentality which has it's own benefits.

    At the end of the day - it's all going to shift with Web3 so in reality not just React will die ((I Don't think it will die at all, it will either mutate/migrate or be replaced maybe with new standards to support the future web standards)) but all current frameworks/libraries are going to shift focal points in the next 5-10 years - there's no telling where we will be. Either way imo React isn't this 'big bad' enemy your making it out to be - if anything React helped me finally grip some Javascript principals I never understood before because I was able to actually implement them with React and see them working, without a bunch of confusing JS I didn't understand I did understand what was happening and I understood how I made it happen.... I just took a little shortcut to get there - and isn't that the essence of programming? Finding the quickest, functional, most viable solution to a problem?

    I'de revise the title none the less React has a huge community of very loyal, and supportive folks and they gonna hammer this post to no end unless you come with some more factual information not so much opinionated concerns with the logics and principals.

  13. 2

    It's like saying "You shouldn't learn C because you would be missing out on learning Assembly" - what a dumb take

  14. 2

    React can't keep developers from learning fundamentals. The normal, right way is to start with fundamentals, then move to frameworks like React. If you do it vice versa you will never be a good developer, that's it.

  15. 2

    Lol. Same as PHP, it keeps dying every year 🤣

    1. 2

      'Dying' .... yet still 71.5% of the web is in PHP (wordpress) ... It's hard to read sarcasm through comments lol

  16. 2

    Time to learn Svelte eh?

    1. 2

      Just picked up Svelte after using Vue. Life changing man

      1. 1

        I was very curious to learn Svelte but not much update from the framework now a days. Or Am I missing something?

        1. 1

          Plenty of new stuff in svelte. Esp sveltekit.


  17. 2

    I hear a similar refrain from people who say VSC is going to die, meanwhile it's the #1 most widely used editor out there by a long shot.

    But if there is one framework that is gaining ground its NextJS. Everyone seems to be talking about it, and last year it wasn't even on anyone's radar, while this year it's actually getting mentioned along with React, Vue, Angular, ect.

    To me, I like React simply because I can write in JSX, so I'm not going to give it up anytime soon.

    1. 1

      You do realize NextJS is React right? lol

    2. 1

      Next.js is built on top of React.

    3. 0

      "I hear a similar refrain from people who say VSC is going to die, meanwhile it's the #1 most widely used editor out there by a long shot."

      SublimeText was once the #1 most widely used editor by far...until it wasn't.

  18. 1

    I'm not sure that I agree with the idea that "React's days are numbered" but I've actually been moving more towards server side rendering using templating and then styling the frontend with tailwind or bulma. For interactive components, I'll use small amounts of JavaScript, but I've just started to look into htmx as an alternative. Admittedly, I am more of a backend engineer, so have a very light frontend is very appealing to me.

  19. 1

    react is one of most powerful and amazing language . I always prefer react

  20. 1

    I think Next changed the React game for me so fundamentally that I'm sticking with it for now. Very curious about Svelte but at the time had concerns about the size of the ecosystem especially with regards to things like auth.

  21. 1

    React just became classic 🙌

  22. 1

    I learned react like 2 years ago, and after running into the multitude of different frameworks, I haven't used it in quite a awhile and not sure if i'm going to get back into it

  23. 1

    I agree that React can keep developers from learning many of the fundamentals of web development (like the basics of the core web technologies, HTML, CSS and JS.) But that's not a reason not to learn React. It's just a reminder that the rest is important too, imo.

  24. 1

    Secondly, React requires extremely complex build tooling that ultimately reduces code maintainability.

    Rails has been trying to solve for this in Rails 7 with their own toolbox like Hotwire. Curious to hear if anyone has any experience with this new tech.

  25. 1

    That's like don't learn assembly or don't learn C...

    You look at F35's cost per line of code and you'd wonder why you even bother learn js or do any other job...

  26. 1


    Off-topic question - I'm a new user on Indy Hackers and haven't figured out all the tricks yet, how can I publish a post like this with a picture, an announcement, and a headline like yours? Can you suggest?)

    1. 1

      this (the above post) is a link post. just click on "new post" and then you'll see there's an option of submitting a "text" post or a "link" post.

  27. 1

    Wrong. Or the title is at least.

    React is an amazzzzing tool to help you build scalable indiehacker apps and websites.

    Now I agree that HTML, CSS, JS, and other fundamental web concepts are important to know before learning React.

    Please fix the title. It is absolutely misreading and most of the people commenting here are just annoyed with you.

    1. 1

      what is the distinction between an "indiehacker app or website" versus a regular app or website?

      1. 1

        But yes, I sew what you mean. React is great for a lot of things! ✨

        Just when talking about SaaS websites and applications, React is awesome for it

      2. 1

        Meaning a site made by indiehackers.

        For example NBA.com isnt made by indiehackers, but plausible.io is.

  28. 1

    You still need to learn css and understand html with react

  29. 1

    Even if React was to loose popularity in the short term, it's so popular that it will not go away anytime soon

  30. 1

    hmm...although React is used widely, people don't seem that satisfied by it as they once were.

    The framework I've seen really pick up steam against it recently is Vue. The only drawback of it would be there is just less documentation and community compared to React and Angular. However, it is easier to understand and going get with compared to React/Angular (but overall there is a lot of overlap between these frameworks, namely that all 3 are using JS behind the hood).

    1. 1

      A small warning about frameworks like Vue. If the user's browser is old, Javascript is disabled, or some javascript file fails to load, then you're likely end up with a blank page.

      I saw advice a year or so ago, that you should try to make the website work okay without javascript, and use javascript to enhance the UX

      1. 2

        I'd say tiny warning. If user is about to use a web app, JS turned On is a must, in 99.9% cases. Trying to serve 100% visitors is not a good idea for solopreneour, so, my suggestion would be to just show the "please turn on JS" warning if JS is off.

        1. 1

          IIRC, his argument was that a sizable number of those who supposedly don't have Javascript enabled, actually do, but the Javascript file(s) fail to download. You may have experienced this, when a site started working properly after you hit the refresh button...

        1. 1

          No idea about nuxt. I tried Vue out with an outdated browser (good enough for Bootstrap 3 & jQuery), and every Vue example site completely failed with a blank screen.

          1. 1

            Any JS framework fails with the browser that doesn't support Javascript. You can probably fix this by using server-side on your website.

            1. 2

              True, although it's not just a does/doesn't support Javascript issue. The browser I tested Vue with has Javascript, it's just several years out of date.

              Some frameworks/designs fail more gracefully than others. Vue stuck out, because I ended up with a completely blank page.

  31. 0

    I think React is getting more trendy now. Why not bother learning it?

  32. 0

    Agreed. Learn Vue 3 and the composition API.

  33. 0

    Very interesting read. Thank you for this useful insight. I just wish some private colleges in Zagreb would heed this advice and stop teaching students React and get with the times...

  34. -2

    This comment has been voted down. Click to show.

Trending on Indie Hackers
I failed 5 startups, what next? 37 comments Users want to use social logins 34 comments Do you have a blog for your business? If not yet, why? 28 comments What I've learned building an indie SaaS business 28 comments How to learn hard things in tech 28 comments 26 actionable marketing tasks you can do right now 14 comments