3 ms·
I think CRA's core audience is people like me - JS noobs. I have no idea about all the things I need to do to start a JS project or how to get it deployed. CRA
by nindalf 7y ago
I think CRA's core audience is people like me - JS noobs. I have no idea about all the things I need to do to start a JS project or how to get it deployed. CRA tells me - "just run this line and you're good to go". The goal is lowering the barrier to entry by giving sane defaults.
Will I understand everything that's happening? No, but that's a non-goal when I'm starting out. The hope is that I get started, google the stuff I don't understand and gradually understand all the components and why they're there. When I become a JS pro, it's possible the sane defaults won't work for me and I'll choose something else, with an approach similar to yours.
- acemarke 7y agoI'm a JS and React _expert_, and I still use CRA all the time whenever I want to spin up a new project because I don't want to take the time to mess with all the build setup. I just want something that works right.
- jakelazaroff 7y agoSame here. Debugging build issues might be one of the most frustrating and boring parts of development, especially because 99% of apps need basically the same setup. CRA gets a new app with good defaults up and running in like thirty seconds. And there’s no magic — if you outgrow it you can always eject.
- nindalf 7y agoI said "it's possible I might choose your approach", meaning the option is open to me - CRA defaults or completely custom. You have the option to go either way. Whereas a noob should just use CRA.
- acemarke 7y agoRight, I was just trying to clarify that even as a non-newbie, CRA has benefits and is my tool of choice.