i feel so validated in that when someone first pointed me to "create-react-app" (several someones actually) like it's a normal way to do frontend dev in the year 201X/202Y i ran it, concluded the output was dogshit, got into a minor fight over it and then never touched it again
turns out it is in fact dogshit, professionals agree!
i was porting a c++ app to the web and the node_modules folder alone had more files and more bytes than the entire c++ part. by more than an order of magnitude, if i recall
i'm not a javascript hater (i think modern JS and TS are pretty good all things considered!) and i'm not even a react hater (i maintain two react apps! not apps-pretending-to-be-websites, actual applications); i am however definitely a create-react-app hater. i cannot imagine why you would actually want this abomination
@whitequark oh definitely, it's just hiding all that config in the node_modules and the only (documented) way to make any modifications was to adopt the overcomplicated configuration into your project, leaving you with no way to update ever again without days of effort.
But at least it got you started quickly I guess. Never used it on a serious project myself.
@truh it most certainly did not get me started quckly because my step #1 when encountering a new environment is to take it apart to understand how it works :p
and even the configuration without the hidden bits was pretty challenging to wrap your head around
✧✦Catherine✦✧
truh