wincent

By Elijah Newren, author of Git's newer mergeort merge algorithm. ("ort" or "ostensibly recursive's twin" replaced the older recursive merge algorithm.)

1.3 MB download.

Me too. Sad to say just how huge the quality of life improvement from this small tweak.

> why would the Prettier team fund another project!?

Less "the team" per se, and more vjeux, I think.

Literally unplayable.

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.

Eyeing you jealously from my position at 237,014 on the list... We're almost neighbors, I guess.

> Maybe it's Ok to be a little hungry.

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.

Towards the end:

> 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 get annoyed because I have to work around C's warts to do what I want, and that is only happening because I think in my language

You "just" have to get to the point where your compiler is written in your own language. This may take a while. Go got there in V1.5:

https://go.dev/doc/go1.5

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.

Wish the font was a bit bigger on mobile though.

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).

You can have it clone your dotfiles repo automatically and run a set-up script:

https://docs.github.com/en/codespaces/customizing-your-codes...

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.

https://jacobbuckman.com/2021-05-29-please-commit-more-blata...

I'm trying to work through this lately and finding it hard: findings so far — https://wincent.com/wiki/Modifier_keys

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.

Some related discussion from a few months back (specifically, a critique of hooks): https://news.ycombinator.com/item?id=22995928

FWIW, I think the single tweet that sums up the reason why hooks are the way they are is this: https://twitter.com/sebmarkbage/status/1094093984211787776

> 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.)

Another Ranger-like that is worth a look is "lf", written in Go, and in my experience faster: https://github.com/gokcehan/lf

> I think the most dangerous distractions are the ones that feel productive but don’t actually work toward your goals. For example, browsing hacker news.

Browsing HN has never felt productive to me. At times useful, entertaining, informative, thought-provoking, and at others less so, when it can seem annoying, repetitive, pointless and so on. But never "productive".

Another nice thing about Capture One is the speed.

I had a similar set-up and did some screencasts on it a few years back (link below). It worked well, and was the least-sucky thing out there for plain-text email, but in the end I just got fatigued at continuously having to switch to another viewer (a browser) in order to properly see HTML email, which was ubiquitous. I ran back into Gmail's loving embrace, not happily, but reluctantly.

Overview is here: https://youtu.be/obY1um6ehDM

Chrome won't load that without the trailing dot: http://dk.

I don't know about how the photo was originally presented, but the tweet that I linked explicitly says the frame is "17 30-second images of the comet added up", so it's hardly disingenuous.

The impact of Starlink on astronomical observation is in dispute and by no means is a settled matter: https://en.wikipedia.org/wiki/Starlink#Criticism

This photo was doing the rounds a few days back showing starlink interfering with ground-based space photography: https://twitter.com/djulik/status/1286053695956881409

Also: https://en.wikipedia.org/wiki/Space_debris

pg: What's your HN username?

ta1234567890: ta1234567890

pg: Hm, doesn't ring a bell... [looks awkwardly into cocktail glass]

I really wanted to switch to Firefox, but after several weeks the thing that pushed me back was janky scrolling. It seems like a trivial thing, but it absolutely drove me first up the wall, and then back to Chrome.

> Again, seeing the failure of the LHC and then deciding you're going to double down is just straight irresponsible.

Not to take away from your larger point, but describing the LHC as a failure may be wording it a little bit too strongly. The fact that it confirmed the Higgs Boson seems like a reasonably important experimental result.