I don't understand why you'd want to advocate for creating a new monopoly. Having a rich, diverse market of competing search engines would be the ideal.
That's part of my point. We already tried a rich, diverse market of competing search engines and it still ended up in a monopoly. In fact I would argue it was inevitable.
At least this way the site owners get to choose their monopoly master. So in a way it's democratized. If Google can be blocked successfully (big IF), then Kagi can as well if they change their tune.
It's arbitrary to a degree like the difference between using an attribute or child element in XML, but it's not entirely arbitrary. If you want to include data in the URL that's not part of the hierarchy of the path, query strings are good for that.
I still think it pretty much was the last major generational upgrade in graphics. An early PS3 game looked night and day better than a late PS2 game. Meanwhile, an early PS4 game looked only marginally better than a late PS3 game, and most PS5 games don't look noticeably better than a PS4 game.
I don't mind that graphics have plateaued, because they aren't the important bit. If anything, I would rather that devs stop trying to chase graphics and make more games with shorter dev cycles.
> Meanwhile, an early PS4 game looked only marginally better than a late PS3 game, and most PS5 games don't look noticeably better than a PS4 game.
Partially this is because there was usually an overlap in sales for early PS4 and late PS3, etc. if you have to support both console generations, it won’t truly be able to take advantage of the newer gen stuff.
Texture resolution and shadow resolution do a lot to make a game look better. The big difference between the PlayStation 2 and 3 was the massive jump in texture resolution, shadow resolution and model polygon count. Play Gran Turismo 5 and go look at one of the cars imported from Gran Turismo 4 for a good example. However the PlayStation 2 was capable of some very high polygon count models, as evidenced by Lulu's cutscene model from Final Fantasy X that rivals most PlayStation 3 player models in detail. Those resolution upgrades, the number of objects and not just polygons displayable on screen, and the increase in distance required for low-poly LOD models all made that giant leap possible and very visible. Since then it's mostly been adding camera effects such as depth of field and ambient occlusion that are much less noticeable. Though for those with keen eyes, only in the current generation are there textures without noticeable anti-aliasing effects which came as a result of being able to split the UVs thanks to a higher resolution making small UV faces possible.
Since we're 10 years on at this point, I feel pretty confident saying the plateau to my eyes landed somewhere between the PS4 in 2013 and Pascal (GeForce 10-series) in 2016.
I've kept playing games and upgrading my GPU every other generation, and they're still fully utilized, but I can't really see where the additional compute and money is going. My biggest visual upgrade during that time was actually going from LED to HDR OLED which is something that requires virtually no additional processing power.
> It matters (to me) because `wget`/`curl` plus `patch` is not some exotic lab setup.
If the point is to be able to do `curl https://...deadbeef.patch | patch -p1`, you can just change the extension provided to Github from `.patch` to `.diff`. That way, it just includes the hunks. E.g.
I've changed my mind regarding the email format not being a problem. I was thinking of emailed git commits as this ad-hoc thing, but I forgot that `git-format-patch` and `git-am` exist. It's not just an incompatibility between them and `patch`. If you have a line `---` in your git commit message, `git-format-patch` will not somehow escape it, resulting in git-am truncating your git commit message. The email commit format is kinda bad. Github `.patch` exports are just being compatible with `git-am`, so I don't think it's a bug with them.
This is Re:
> I do not yet know whether the bug belongs to GNU patch, GitHub’s .patch export, or the broader patch-format contract.
I don't think this is a problem with GNU patch or the patch format per se, just the emailed commit format. I think the patch format's good because it allows it to be embedded in other texts and also allows comments or extended syntax between hunks. For example, the lines
diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c
index 15ba592236e845..725a49a0eee72e 100644
not being part of the hunk and probably being seen as a comment by `patch`.
Simply changing `git-am` to accept commit messages being indented in the email format would allow Github fix the issue of their .patch exports being incompatible with `patch`, in addition to fixing that bug about commit messages being truncated when they have a `---` line.
reply