call me old-fasahioned, but two spaces after a period will solve this problem if people insist on all-lower-case. this also helps distinguish between abbreviations such as st. martin's and the ends of sentences.
i'll bet that the linguistics experimentalists have metrics that quantify reading speed measurements as determined by eye tracking experiments, and can verify this.
( or alternatively use nested sexp to delineate paragraphs, square brackets for parentheticals [( this turned out to be an utterly cursed idea, for the record )] )
You appear to be trolling for the sake of trolling, but for reference: reading speed is determined by familiarity with the style of the text. Diverging from whatever people are used to will make them slower.
There is no such thing as "two spaces" in HTML, so good luck with that.
Code point 160 followed by 32. In other words ` ` will do it.
edit: well I tried to give an example, but hn seems to replace it with regular space. Here's a copy paste version: https://unicode-explorer.com/c/3000
But...the vertical dimensions don't scale so well, at least in my browser. It causes a slight downward shift.
I'll likely continue using Capitalization as a preference and that we use it to express conventions in programming, but I totally understand the movement to drop it and frankly its logical enough.
This is a merely showing off your personal style which, when writing a technical article, I don't care about.
Pointing out that language evolves helps to explain how the current established conventions came to be, but it is not an argument that there are (or should be) no established conventions.
If you are speaking in a way that diverges from what most people understand, then you are miscommunication and are making demonstrable errors precisely because the language has evolved into what it currently is, and not something else.