this post was submitted on 03 Jan 2024
62 points (97.0% liked)

Programming

17450 readers
121 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Corngood@lemmy.ml 28 points 10 months ago (2 children)

It's all reasonable stuff except maybe:

People’s names are all mapped in Unicode code points.

I don't see how you could avoid this this in software that needs to ask the user their name.

I think it's definitely a good idea to avoid using names wherever possible, and definitely don't try to do anything clever with them.

When necessary, software can just be clear:

  • "in unicode, what should I call you?"
  • "in unicode, who is making this credit card transaction?'
[–] Spzi@lemm.ee 7 points 10 months ago

You can do that when you control the frontend UI. Then, you can set up the input field for their name, applying input validation.

But I would rather not rely on telling the user, in hopes they understand and comply. If they have ways to do it wrong, they will.

[–] Semi-Hemi-Demigod@kbin.social 1 points 10 months ago (1 children)

Users: "I don't speak unicode"

[–] Corngood@lemmy.ml 1 points 10 months ago

Haha, yeah, I didn't mean literally telling them that. More like giving them a text field that can only contain unicode characters, which is pretty standard.