vhwalke

Thank you! It's been fun.

These are great thoughts. I may do some investigation into how the Federalist Papers spread, but even with AI, these may be significant research efforts. I need graduate assistants!

Thank you! AI clearly helped a ton, but the number of rounds of me having it render different fonts / formats was staggering. And, I was fortunate enough to come across justif (https://justif.lyall.co/) - I found via HN! ... It perfectly implemented the system of justification I needed.

Thanks for the kind words. It has been fun to put together - Hopefully a good addition to the world.

Really hugely appreciated. I'm doing an AI pass at removing some more of the AI-ism's. It came up with some good suggestions. I'm reviewing and should have those in before long. I'm sure it won't be complete, but might give a better starting point.

Thanks again!

Completely a fair point. Definitely was heavily, heavily AI built (including the copy) - there is no way I could have justified putting in the time it would have taken to build this for a "pro-bono" project pre AI! Even with AI, I've spent a considerable amount of time steering, editing, and revising (including some of the most egregious AI adds).

Would absolutely appreciate edits and revisions. Repository here:

https://github.com/vwalke/federalist-papers-reader

Thanks for the feedback! Vann

I spent the past few weeks building what turned out to be a much bigger project than I thought it would be - with more AI assistance than I've ever had on any project, and I've been thinking about this.

In the end, I'm happy with the AI development. The machine laid a lot of bricks. But every judgment that makes the thing itself was mine: which typeface felt right, which historically accurate detail to reject because it hurt readability, what tone the notes should take, what to cut. Some days that feels like making. Some days it feels like being an editor with a very fast staff. Editors are proud of their papers too.

The important part: I built it for my mom. She can't tell which lines I typed and which I asked for. She can tell it was made for her. Maybe that's the part that survives every new tool — who it's for.

And aside from any question of "pride" .... this project would never have existed without AI support. I wouldn't have had the time. Wouldn't have pushed it to the level of excellence that it shows. And, would have been pulled off to other distractions, projects, and work long before it got over the finish line.

It may be a different world. But, I'm all in.

Implemented on https://federalistreader.org ... made a big difference! You can see the comparison here:

https://federalistreader.org/notes/justif/

Nicely done! (and thanks for the fixes with v0.5.0. I submitted a couple more.)

Follow-up, since I asked the questions above: I spent the evening running Justif against the hardest page I have: three 356px columns of 18th-century text set in IM Fell at ~17.6px with 24.3px leading. I came in curious and left planning the integration.

The numbers were better than I hoped. A full ~5k-word essay justified in about 280ms, and ~36KB gzipped including the en-US patterns. And the output is the part that sold me. The columns look like typesetting rather than CSS, which is the whole thing I'd been grumbling about.

The only snag I hit: a floated initial letter (drop cap) trips it — the first line ignores the float and overflows the gutter. Excluding that paragraph and leaving it on native justify renders perfectly, so it's cosmetic to work around, but a first-class exclusion selector would be lovely. I'll file an issue with the details and our measurements.

Best part: this experiment exposed that our sheets are currently set ragged right, which no printer in 1787 would have tolerated. Your library may be what finally makes us historically honest. Test page for context: federalistreader.org/papers/10/

Thank you for building this!

Wow! I've spent the past few weeks setting 18th-century newspaper text on the web - justified, up to three narrow columns, period ligature, and the gap between CSS justification and real typesetting was a big part of the whole project. The browser's greedy line breaker plus hyphens: auto gets you maybe 80% there, and the last 20% is rivers, loose lines, and archaic words the hyphenation dictionaries have never met. "Fœderal" produces some genuinely creative break points. The result I got to I feel like is good, but not great.

Questions, from someone who wants this to work:

* Does Justif do its own hyphenation (Liang patterns?) or lean on the browser's? And is there a way to feed it exceptions for unusual or archaic spellings?

* How does it behave at narrow measures, say 35–40ch columns? That's where Knuth-Plass should shine most, but it's also where badness compounds fastest.

* What's the reflow cost on long documents (5–10k words) when the container resizes or the user scales the text — full re-run or incremental?

* Any thoughts on coexisting with text-wrap: pretty as browsers slowly grow real paragraph-level breaking?

Congrats on shipping this. I miss producing documents with TeX!