React, Electron, and LLMs have a common purpose: the labour arbitrage theory of dev tool popularity: https://www.baldurbjarnason.com/2024/react-electron-llms-labour-arbitrage/
@baldur outstanding.
Another way to express labor arbitrage is "making engineers fungible".
Daniel Sockwell has an interesting video on this with respect to programming languages. https://youtu.be/MCKozTfcWr4?si=dkk17B8hn9Sbefzh
@firebreathingduck Thanks! Will have a look at the video.
@baldur it's 40 minutes, so I won't be offended if you lose interest. But he focuses, for example, on the way Google's Go language tries to make engineers interchangeable while many other languages do not.
(Edit: I am not against Go at all. I just thought the idea is worth considering.)
@firebreathingduck There are many great observations in the post by @baldur, and in this video from @codesections (about the goals of programming groups at big tech vs developers creating "free software").
I see similarities in the tool stacks used in the #DataScience / #DataEngineering realm. It feels like there is a push to use no/low code, cookie-cutter, closed sourse, costly, inefficient, obfuscating tools that make it difficult to verify you're getting the "correct" answer, and a purposeful move away from craft and excellence. Commoditize, commercialize, and cross-#enshittify is the credo.
@firebreathingduck @baldur This is the explicit purpose of Go.
EDIT: I see you mentioned that Go is brought up in the video.
@clacke @firebreathingduck I really enjoyed watching that video. Thanks!