This is missing a text layout engine: separating a string of texts into multiple blocks with word wrap. This is handled in GTK+ through Pango and in Qt with an internal algorithm. I don't believe FreeBiDi/ICU is used in either.
Interesting question, from my understanding Pathfinder is only concerned with rendering so it doesn't completely replace FreeType: you still need some software to extract the curves path data from the font file. This can be done in rust with skribo and font-kit
"Hinting" is a combination of techniques. Subpixel placement hinting is done by the shaper, which would be HarfBuzz in this case. Metrics hinting (adjusting the glyph width) is done by a combination of the shaper and the renderer, which would be HarfBuzz and FreeType. Outline hinting (fitting outline to the grid by distoring shapes without) is done by FreeType.
It's important to make the distinction between subpixel positioning and subpixel (RGB) rendering. I'd personally say yes to the former, even at high dpi, and no to the latter if you're on a mobile device. The kerning errors you get from quantizing the position of glyphs to integer pixels are, to my eyes, a noticeable degradation of quality.
Most laser printers tend to use PostScript (a Turing complete language), which does not know about displays hardly at all. It does arbitrary positioning.
I don’t know the details, but on my 4K screen different applications font rendering looks very has a very noticeable difference in quality. Eg IntelliJ looks great, and afaik uses some form of subpixel Rendering. Where’s VS Code looks kind of crappy since the update to macOS Mojave, which as far as I understood changed font rendering
Yeah, at distances people actually view displays at, there is still a benefit to subpixel rendering and some amount of hinting, even on "retina" displays.
Far as I'm concerned, high res displays help hinting do less damage, but they don't render it obsolete.