Even then, Apple took enough care about every aspect of design, materials, and manufacturing that they could non-ironically show a high detail photo of the back of the machine on the back cover. Not only is it delightfully quirky; it's beautiful, even today.
I've been blogging, albeit not consistently, for 25 years or so. I don't even know how many readers I have, because I don't do any analytics.
When I write, it's for me, for the pleasure (and sometimes pain) of ushering thoughts out from the unstable flickering of my consciousness and into the realm of the fixed and concrete word. Well, as "fixed" as these kinds of digital artifacts ever are, I guess.
Sometimes people write to me to share their thoughts about something I wrote, and that's cool,but it's not the reason I'm doing the writing.
This is the key. On evolutionary time scales, human beings have only very recently come to inhabit a world where regularly being able to eat to full satiation (and beyond) is commonplace. Being "a little hungry" is actually the typical condition under which most of our ancestors over many thousands of years have operated. Put an organism evolved to survive amid scarcity in an environment of abundance, and it's going to gain weight unless it comes up with a method for stopping at or before the earliest signs of satiety.
> In addition to vertical partitioning to move database tables, we also use horizontal partitioning (aka sharding). This allows us to split database tables across multiple clusters, enabling more sustainable growth.
Linked in the article is this other one, "Partitioning GitHub’s relational databases to handle scale" (https://github.blog/2021-09-27-partitioning-githubs-relation...). That describes how there isn't just one "main primary" node; there are multiple clusters, of which `mysql1` is just one (the original one — since then, many others have been partitioned off).
I think poster is saying turn _off_ "Automatically install updates" but leave _on_ "Check for updates [Daily/Weekly/Monthly]". That way you at least become aware that updates are available, and can assess them for yourself.
It always bugged me that the proof went on the profile itself and not on a mere comment like it does for other identities (Twitter → tweet, Reddit → a post in /r/KeybaseProofs etc).
I also have a very bespoke dotfiles config that predates Codespaces (https://github.com/wincent/wincent), so I made a thin wrapper around it that makes it work (https://github.com/wincent/dotfiles). For people with less complicated set-ups (ie. basically the entire universe), it is pretty straightforward.
GitHub isn't forcing anybody to use a web IDE. The most broadly used access interface is VSCode. Then there are heretics like me who choose to ssh in so we can use Vim. This is described in the article.
Best part of the article is the footnote, where the author characterizes his own papers:
> This paper is bullshit, this paper (a NeurIPS oral) is bullshit, this paper is complete bullshit, this paper is mostly good science but also has a sprinkling of bullshit. Apologies to my co-authors.
Biggest hurdle is finding a clean way to do application-specific overrides, because even if you can get the general case working right, there is a lot of per-app variation.
> A property of Hooks is that it forces you to confront them early and then you just learn patterns that don't have the same issues. I don't know if that is worth the tradeoff, but I stick to the claim that this is the tradeoff.
(That's Sebastian Markbåge, who's basically been chief architect of all things on the core React team for the last 5 years or so.)