3 ms·
Sure, but you can't always fix the bug if it's not in your system.
by panstromek 9mo ago
Sure, but you can't always fix the bug if it's not in your system.
- mgaunard 9mo agoFork it, you should have ownership of your whole stack. If you have the spare time, you can try and submit your patches upstream; in the meantime, you just maintain your own version.
- panstromek 9mo agoNo, you can't always do that. We have workarounds for platform bugs that were even fixed, because we get users with old devices that can't upgrade. You cannot fork a phone of a random person on the other side of the world. Once a platform bug is out, it can stay out in the wild for a very long time.
- mgaunard 9mo agoDeploy your own platform -- if need be built on top of other (unreliable) platforms.
- panstromek 9mo agoOur website codebase contains a workaround for a bug in native Android file picker in Samsung One UI. How are you supposed to solve this by "deploying your own platform?"
- mgaunard 9mo agoBy decoupling your application logic from your UI toolkit.
- panstromek 9mo agoSo, when operating system gives you invalid file, it magically becomes valid, because your UI code is in a different file. Sure, that sounds plausible.
- mgaunard 9mo agoI suggest you read up about encapsulation. Have a good day and happy new year!