4 ms·
> No one would blame you for choosing React for a major project / new startup Oh, I know people who would. Especially if that choice was made mechanically, wi
by azangru 4y ago
> No one would blame you for choosing React for a major project / new startup
Oh, I know people who would. Especially if that choice was made mechanically, without proper assessment of project requirements and framework strengths/weaknesses.
- actionfromafar 4y ago"Nobody ever got fired for X" is a rhetorical device which means "in most situations, you generally won't be faulted going with the most main-stream option on the market".
- mellosouls 4y agoTo be fair, as frustrating as it is sometimes for those of us who want to use the best tool, for those who have jobs affected by the risk in their decisions, it's a sound principle to default to.
- solardev 4y agoI think the nuance is that much of the IT world moves much, MUCH slower than the web frontend. "Nobody ever got fired for choosing IBM/AWS/Google/Microsoft/ESRI" will culturally last a loooooong time (5-10 years? 15?) "Nobody ever got fired for choosing jQuery? Angular? React? Vue? Svelte? NPM? Yarn? Node? Deno? Next? Gatsby? Netlify? Webpack? Parcel? Babel? Bun? Canvas? WebGL? WASM? Workers? Cloudflare? Fly? Leaflet? OpenLayers? Mapbox?"... that has what, a lifespan of 2-3 years at best?
- azangru 4y agoNobody ever got fired for choosing standard browser technologies, I would have thought :-) Which, from your list, would include canvas, webgl, wasm, and workers. As for the rest — they may very well have been :-)
- solardev 4y agoWell, there are a lot of abstractions over those. Canvas by itself in the raw isn't very useful without a framework on top of it. Same for the others, except maybe Workers...
- mritchie712 4y agoI mean this from the perspective of a newly founded startup. You're right that this doesn't hold true in a large corporation where they may already have a ton of code and preferred frameworks.