- cross-posted to:
- hackernews@lemmy.smeargle.fans
- brisk ( @brisk@aussie.zone ) 6•8 months ago
I’ve seen far too manny error messages claiming I did something I most certainly didn’t do. This seems like a good way to make those far more prolific.
- Fontasia ( @Fontasia@feddit.nl ) 1•7 months ago
Isn’t this better to understand about what the program is trying to do, which a user really only has a passing influence on
- zartcosgrove ( @zartcosgrove@beehaw.org ) 3•7 months ago
This seems wrong to me. Existing paradigms like try catch or returning result codes enable handling these situations gracefully and in an informed manner. Making an inert api as is suggested here means that now you have an api that doesn’t behave as expected but without an explanation why.
“The app was probably only tested against a PC so an exception would be unhandled” means that they did not implement it well against a PC. There are a bunch of possible reasons you’d get an exception while adding a printer on a PC, and I can’t imagine that the correct behavior would be to crash whatever it is you’re doing.
- 💡𝚂𝗆𝖺𝗋𝗍𝗆𝖺𝗇 𝙰𝗉𝗉𝗌📱 ( @SmartmanApps@programming.dev ) English1•7 months ago
How to be inert.
Be alert - the world needs more lerts