News for hackers. Stuff that matters.
Re:Android’s Commitment to Kotlin by izacus on Saturday December 07, 2019 @04:57AM (#21729410)
Because the alternative is not resetting the state and having to deal with the fallout. iOS does this and it's a source of even more strange bugs and side issues (based on doing cross-platform development across several teams).

This even led to the point where a huge amount of iOS apps simply banned rotation support to not deal with it.

It's just a different tradeoff. The underlying issue is that developers don't want to deal with storing the state which causes issues on lower end devices, which start to break as users multitask. The Android tools for that also aren't all that great - although I also haven't really seen any other toolkit do it better.

Re:Android’s Commitment to Kotlin by cerberusss on Saturday December 07, 2019 @06:30AM (#21729710)
I'm an iOS developer and I'm not sure what you mean. Auto Layout provides enough hooks to take care of rotation. Why would rotation be a source of strange bugs and side issues?
Re:Android’s Commitment to Kotlin by izacus on Saturday December 07, 2019 @09:42AM (#21730484)
Because not all the state and layout is handled by AutoLayout... and it has its own set of bugs. Heck, iOS apps themselves (iMessage, Springboard) and riddled with rotational layout bugs in iOS 12 and 13.
Re:Android’s Commitment to Kotlin by cerberusss on Saturday December 07, 2019 @09:57AM (#21730565)
But how bad is it, I mean how many have you encountered so far? I don't doubt it, but in my years of iOS development, I haven't seen them.