Done to this awful extent, it's not just a stylistic choice but a UX error. Human brains optimized for reading initially recognize words and phrases based in pa

Done to this awful extent, it's not just a stylistic choice but a UX error. Human brains optimized for reading initially recognize words and phrases based in part on their shape, and orthographic conventions like initial majuscules and bullet lists evolved to facilitate that recognition in support of legibility. Abusing semicolons in this way is, in the most strictly pedantic sense, not syntactically incorrect inasmuch as a semicolon joins independent clauses. But that's like saying you can use a flathead screwdriver in place of a cold chisel. Sure, if you hammer on it hard enough for long enough, you can eventually muddle through, as long as you don't mind making an unserviceable mess of the work. But it's still the wrong tool - just as are thirty-five semicolons here. Syntactically permissible or not, this usage is nonetheless an error, not because it is stylistically grotesque - although it is also that - but because it actively impairs legibility rather than promoting it.