> That's why we need proper unicode support everywhere.
A couple of years ago when I wrote a little webapp to do some scheduling stuff for our community's yearly conference, I just used plain unicode strings for usernames, including spaces. I didn't really see why not: The database (SQLite) handles unicode, the backend (golang) handles unicode, the frontend handles unicode, nothing ever gets passed into a shell program or put into CSV or anything, all queries are parameterized; why bother making pointless restrictions?
A couple of years ago when I wrote a little webapp to do some scheduling stuff for our community's yearly conference, I just used plain unicode strings for usernames, including spaces. I didn't really see why not: The database (SQLite) handles unicode, the backend (golang) handles unicode, the frontend handles unicode, nothing ever gets passed into a shell program or put into CSV or anything, all queries are parameterized; why bother making pointless restrictions?