666 karma · joined May 15, 2023
Goldilocks went inside the Git Hut. First she inspected the git repo of the great, huge bear, and that was 2TB which was far too large and monolithic for her. And then she tasted the 281 repos of the middle bear, and they were far too small and numerous for her. And then she went to the 10 repos of the little, small wee bear, and checked out those repos. And they were neither too large nor too small and numerous, but just right; each had it's own reason to be and she liked it so well, that she sat down and cloned it all.The most frustrating thing for me is fucking Google. Their search results are so bad these days I can't get my game to the top even though thousands play it every day and link to it on social media. I'm at the top of Bing, DDG, Kagi. These sites run links to each other and Google's dumb algo loves it. Usually they don't use iFrame but proxy the whole request. Since using CloudFlare as my CDN a few of the app thieves have been defeated.
Of course there is no smoking gun but you'd have to be dumb to believe it's not happening. Apple want to make phones in China and sell phones to China Wechat (China) is allowed a free pass on the app store.
I'd say it's more than sitting back. Complaining about the loss of manufacturing jobs or immigrants competing for jobs and housing is seen to be poor peoples' game. The middle class want to be (seen to be) wealthy and educated so they'll signal that these trends are nothing to worry about because it's only an issue for the plebs and they're definitely not a pleb with this opinion.
Every technology has it's equal and opposite force.
Smart phones result in dumber people with lower attention spans. Medicine has taken away most evolutionary selection pressure. Modern agriculture paired with car culture means a lot of us are unfit and overweight. Social media makes people less socially connected and promotes unrealistic beauty standards.
Then GraphQL came along to solve the N+1 issue as let you query everything in one network call... but only over HTTP POST so it broke caching on CDNs.
Then edge workers/lambda came to solve that issue. You can also bring your data closer to the edge with replicated databases.
Most newer stacks like Nextjs, Nuxt or SvelteKit behave like a traditional server side rendered page at first and then dynamically load content like an SPA once loaded which is the best of both worlds. They'll also be using HTTP/3 to force-feed a bunch of assets to the client before it even requests them.
Ideally you'd have your data distributed around the world with GraphQL servers close to your users and use SSR to render the initial page markup.
Given that the terminology comes straight of Orwell's 1984 they're barely even trying to hide the blatant power grab with a few cliche excuses (children, terrorism).