Earlier quoted context omitted.
So... even if it's English-only, I can't quickly refer to a price in £ or € or ¥? Or that it's 90°F out? I can't talk about my fiancée? I can't even use “proper quotes”? Yikes. These days, talking about the "benefits" of ASCII-only is like talking about the "benefits" of HTTP over HTTPS, or the benefits of dial-up as opposed to broadband. No thanks. It's exclusionary and for zero good technical reason. For every reas…
I agree with the overall sentiment of your comment but.. > It's exclusionary and for zero good technical reason. For every reasonable programming language, there are functions to do everything in UTF-8 that you can do in ASCII, with about the same complexity. At minimum, unicode does come with a lot of complexity in implementation, and a lot of potential vulnerabilities due to that complexity. Not saying that excuses…
As far as I know, ASCII is a proper subset of UTF-8. That makes implementation quite natural in most cases (e.g. string replacement).
EDIT:
Looks like Lucian built this site in PHP, which easily handles UTF-8, as well as most DBs.