3 ms·

Exactly, something like a name missing shouldn't cause the app to completely error out for the user.

• slooonz 11mo ago
  Yes it should, because hopefully errors are logged and reported and can be acted upon. Missing name doesn’t.
  • noman-land 11mo ago
    Why not both?
    • rustc 11mo ago
      That's how you get this feature: https://wiki.php.net/rfc/deprecate-bareword-strings https://wiki.php.net/rfc/deprecate-bareword-strings. tldr: undefined constants were treated as a string (+ a warning), so `$x = FOO` was `$x = "FOO"` + a warning if `FOO` was not a defined constant. Thankfully this feature was removed in PHP 8.
  • pitched 11mo ago
    If the error isn’t repairable by the user, blocking them from using the app entirely is mean. If the error screen has a message telling the user where to go to set their name, that’s fine but annoying. If the error screen tells the user they can’t use the app until someone checks a dashboard and sees a large enough increase in errors to investigate, that’s a bigger problem.
  • jackblemming 11mo ago
    This reads like a dogmatic view of someone who hasn’t worked on a project that’s a million plus lines of code where something is always going wrong, and crashing the entire program when that’s the case is simply unacceptable.
    • mystifyingpoi 11mo ago
      > something is always going wrong I hate this sentence with a passion, yet it is so so true. Especially in distributed systems, gotta live with it.