:wave: When I make a mistake and end up causing an...
# compose-desktop
p
👋 When I make a mistake and end up causing an exception in my compose code, it looks like the default handling is to just log it and keep going. Is that expected behavior? On Android the default behavior is to crash, and that’s kind of what I expected. Should I file a bug?
c
I think when I did javafx dev for like 4 hours a few years ago I noticed the same thing. I expected a hard crash, but it just logged and continued. /shruggie
r
Log and continue is the default behavior with AWT, Swing, etc.
JVM really
☝️ 2
k
Desktop apps kinda are not expected to crash and disappear on every single exception
c
lol. you'll have to excuse myself since ive basically only done android dev my entire life.
compose desktop is helping me expand though
p
👍 That’s fair, though maybe devx can be improved by having some way to surface this just happened instead of “mmm weird UI stopped responding let’s go look at the logs”
k
If you're writing an application for somebody else, they really don't care about your exceptions. They don't want to file bugs. They don't want to look at the logs. They want to get a thing done and get on to the next thing. Surfacing "X just happened" is useless.
🤔 1
c
I get your point. Just curious why this wasn't a thing in android? pardon the ignorance but ive only ever done android dev and so i just thought "this is how exceptions work" lol. I'm trying to wrap my head around why'd you want a system that threw uncaught exceptions and it just kept "working"
k
You can see some of it in Android as well, as the system has reduced the "prominence", if you will, of the ANR dialog. If the app is misbehaving, there's not much the user can do really. See how IDEA is minimizing the exposure of its own exceptions. There's a tiny red icon in the bottom right and that's it. As a developer, you live and breathe your codebase. None of your users do, however.