I know nothing about Git development, but it surprised me that most of the changes are kind of internal and affect the end user only on security or performance level.
For some reason, I was thinking there would be more new shiny features. But maybe for the tool that is as mature and wide-used as Git, that's not how it works.
> Some time ago (1999-ish) [...] a number of ways to integrate ads were discussed.
> One was to show a cool video from a respected company (such as Nike) every time the Mac starts up. [...]
This sounds so weird in 2025. However, I can see that probably in those times there was no "norm", and people were trying different things.
Who knows, maybe if it weren't for Steve Jobs, ads at startup might be the norm. And who knows how many similar things we dodged because of people like Jobs.
Kindles have been showing ads on their lock screen for the ad-supported tier for a very long time now.
These days, we have moved to far more insane schemes. E.g. smart TV manufacturers are patenting detection of static frames to show you ads while TV is idle (although I don't think anyone has actually shipped that yet).
Although the article is completely on point, I disagree that theme should be stored in URL.
Imagine you’re browsing a site, and at some point you switch from light to dark theme. After some time, you press “Back”. Do you really expect to switch back to light theme, and not to go to the previous page?
I've seen a lot of “well‑behaved” sites, that are storing their state in the URL, but I've never seen one, that stores current theme.
It’s interesting that the theme is part of the state too, yet you don’t want to store it in the URL. So, this means not every part of the state should be stored in the URL? Then what's the criteria for choosing what to store, and what not to?
When using ChatGPT audio transcription, sometimes it adds to the end “Subtitles created by ...”, and then some username. Obviously, an artefact of training on subtitiles dataset.
