3 ms·
I disagree. The fact that Google has such a power over the shape of web traffic, along with a few other websites, absolutely re-shapes the Internet to fit whate
by marginalia_nu 4y ago
I disagree. The fact that Google has such a power over the shape of web traffic, along with a few other websites, absolutely re-shapes the Internet to fit whatever its standards make a website rank well. It's in many ways almost exactly the same process as natural selection. Whatever works gets traffic and gets copied by other websites, whatever doesn't fades away.
- alexalx666 4y agoyes but we can build our own query tools, for ex. Im using `$ so graphql vs sql` and such terminal commands more and more these days
- marginalia_nu 4y agoOh yeah, this is primarily a problem for Google. They're sort of stuck being chased by the shadow they cast. I've had very little problems cutting through the SEO spam running an independent search engine, but then I don't shape traffic like they do.
- hn_throwaway_99 4y agoSorry, unrelated, but your comment hit a pet peeve of mine. I love GraphQL, and I think it has a number of features that make it better and more usable for most APIs than a RESTful interface. The thing I despise about GraphQL is they put "QL" in the name, so legions of software developers think that it is somehow comparable to SQL, or somehow is a generic query language for data. GraphQL has absolutely nothing to do with SQL. Comparing "GraphQL vs SQL" is like comparing "HTML vs Java".
- alecbz 4y ago> somehow is a generic query language for data. In what sense is GraphQL not a generic query language for data?
- 8n4vidtmkvmk 4y agobecause it's not? it's got no "where" clauses or transforms built in and anything of the sort had to be custom built. you can't query any data in the database, only what the API chooses to expose. it's anything but generic. even pagination isn't standardized
- hn_throwaway_99 4y agoGraphQL is a format and contract for exposing APIs, just like REST is a structure for exposing APIs, just like SOAP is a format and structure for exposing APIs, just like gRPC is a format for exposing APIs. Those are all the right analogies for comparing GraphQL. GraphQL doesn't say anything about how the underlying data is queried - at the end of the day it's just a bunch of resolver functions that you can implement however you want.
- deleted 4y ago[deleted]
- bagacrap 4y agoI think the analogy to natural selection is apt. So is it really Google's fault? Seems like a consequence of a fitness function. And even if there were 4 competitive search engines in the world, each spammy site would optimize for one (or would even have 4 versions that each optimized for a single search engine).
- luckylion 4y agoIf nature was a conscious entity that optimized for some goal, I think we'd say it would be at fault. I'm sure it's not Google's intention to ruin the web, it's just something they happily accept as a by-product of their optimization strategy towards maximum value extraction via ads. Like some chicken farmers happily accepting creating chicken hell because it lowers cost. I don't think they set out to torture chickens and go "hey, I'll start a chicken farm as a cover story".
- marginalia_nu 4y agoIf you had multiple search engines, say four of them like in your example, then the rewards for successfully specializing in either one of them would be a fourth what it is now, meanwhile you would have to put in four times the work to maintain four versions of the site, you would have to conduct four times as much research to maintain your advantage. The economies tip to make specialization less rewarding. Just as in nature, monoculture rewards specialization, whereas ecological diversity rewards generalization. Not that specialization doesn't exist in diverse ecosystems, it's just not as devastating.