4 ms·
But this speaks to good architecture decisions, right? If they tried to make a shared framework that ran the same codebase everywhere and then port it onto dif
by snovv_crash 5y ago
But this speaks to good architecture decisions, right?
If they tried to make a shared framework that ran the same codebase everywhere and then port it onto different platforms (cough facebook) then you don't get these nice isolated issues, for example.
- vadfa 5y agoYes, if you don't write a native app for every platform the result will be rubbish. That's not a "good architecture decision", that is common sense. If they don't do it that way it's to save money, because as we all know Facebook is strapped for cash. (Talking about Facebook and Instagram here, because as far as I know WhatsApp is completely native on every platform)
- snovv_crash 5y agoThis then also means a well defined server API without undocumented behaviour that individual implementations depend on. I stand by my assertion that the good scaling and separable builds is a sign of good architecture.
- vadfa 5y agoIsn't a non-leaky abstraction a given too? All these requirements are like saying "having a good experience using this app requires an app that doesn't crash all the time". Well, duh?
- snovv_crash 5y agoLife would be a lot easier if good engineering practices everywhere were a given.