Gregory's Server@slightlyoff When you say "efficiency", what are you referring to? Development efficiency or the efficiency of the code running on the browser?
I'm curious, as I can agree with one but not the other.
|
8 comments
 @mensrea @slightlyoff Right. Then I agree since react pages are anything but efficient. 🙂  @loke @mensrea Sorry for being obtuse; lots of orgs have picked up React because they were told it's industry-standard, that they would be able to hire for it easily, etc. etc. It turns out that React on its own doesn't get you very far, and so there's a ton of time and money that needs to be spent either building infra to support some agglomeration of state tools + SSR configs + component libraries, or investment in learning metaframeworks like Next. The savings never materialise.  @slightlyoff i think there is another aspect to this. the "modern way" with frameworks, language abstractions (typescript), build pipelines, et al. make people think they're doing "real programming". so they keep layering complexity to solve problems caused by complexity because they're really smart @loke  @mensrea @loke @slightlyoff This. React is the ultimate in inefficiency. The goal isn't to be efficient but to maximally disempower and make fungible the labor involved. @dalias @mensrea @loke @slightlyoff That's it! Project management styles and tech choices are both shaped by the need to make the work of programmers predictable and measurable. Huge costs are incurred, and seen as entirely worthwhile.  @loke @slightlyoff Sounds like profitability is all. The less money handed to developers and customers out of the current revenue base means more money handed to shareholders. |
@loke efficiency as in hot swapable developers because we can't be bothered to put resources into staff retention @slightlyoff