4 ms·
> It's fine to use whatever tools you consider most appropriate for your situation and use case. 1000% agreed. The part where this breaks down for me is the o
by bob1029 3y ago
> It's fine to use whatever tools you consider most appropriate for your situation and use case.
1000% agreed.
The part where this breaks down for me is the observation that many developers don't seem to have conducted the barest of due diligence regarding what tools and options are even available.
I can accept that you went with ReactJS, but not if you are operating in a vacuum where access to MDN is restricted and you didn't even consider the merits of a "no-build" web ecosystem.
- ImPostingOnHN 3y agoI think it's common for someone who prefers X to believe that another who hasn't chosen X has made an uninformed choice, or not done their due diligence (and of course the person believing this, considers themselves informed, etc). This belief is 1 step away from believing that everyone who didn't choose X is wrong. It's actually pretty likely they did sufficient due diligence, and picked the better option for them. Personally, I believe if they found something that works, more power to them. In all likelihood, the "no-build" option is likely more time and more work than using frameworks, for the sort of non-basic web apps someone might choose them for. Doing a comprehensive due diligence of all the possible ways to build something is, imo, the sort of analysis paralysis that stops hackers from just going out and building. Yes, you could become an expert in the full stack, such that you could build an app omitting any or all of them. Or you can build a thing. You're going to throw the first one away anyways.