Re:The art of Front end Engineering
by nawgz on Saturday June 12, 2021 @03:15PM
(#27486788)
I’m not sure I agree with your takes on frameworks. It definitely depends on what you’re building, but in React to have composition and reuse for free immediately sets it apart from any bespoke solutions. I’m also struggling to imagine how you propose to out-scale the React framework with early & tough design decisions... these are Facebook engineers that made those same decisions, and they managed to scale the framework to Facebook levels. You understand that they may be the UI leaders of the world, yes?
[ Parent
| on HN ]
Facebook, the product, did not use React until very very recently.
Do you use FB? If Facebook’s interface represents the “UI leaders of the world” we’re in troubled waters!
Can you say more about why we'd be in troubled waters for such a thing?
Facebook and its non-titular products are probably used by the most people in the world. The org is 50k people, and I imagine their engineering staff is proportionally quite large - they rarely introduce bugs and seem to have quite a good update cycle. There is a huge featureset and the website performs very well.
Re:The art of Front end Engineering
by jazzyjackson on Saturday June 12, 2021 @09:34PM
(#27489029)
> the website performs very well
IME you could measure page transitions in seconds, it is an extremely slow website
Re:The art of Front end Engineering
by austincheney on Saturday June 12, 2021 @11:37PM
(#27489544)
If composition is your first concern you lack vision. Instead start from a good idea, form a vision on how you want to execute that idea, determine what you need, and then build those pieces in isolation. You get separation of concerns for free and composition becomes the last step. If you spend all your energy over concerns on how to build something you are spending creative energy thinking about what cool things to build.