lazerscience

Maybe you can elaborate why this is supposed to be "broken by design"? Django's deprecation policy is one of the best, and also older versions receive (security) updates for a long time. If you're not content with the functionality provided by an open source software there's still much room left to take actively part in its development.

There's not a general solution to serializing child objects, it totally depends on the use case and the number of children. So for example if you have a lot of child objects it might not even make sense to include theirs ids, but have a seperate (maybe nested) resource to retrieve them. On the other hand if there are only few children you might want to include them in their parent resource.

Working incrementally definitely makes sense. Also if you don't see a chance to do it in an incremental way you should probably take a step back and ask yourself if the old application is maybe too huge and monolithic and check if there's a possibility to make it more modular. So you could split one huge application in smaller parts/services which can easier evolve seperately from the rest.

Maybe you can elaborate why you are mentioning them here?

Yes I think this is what the question is about. Some people might call it "Holocracy" or something like that...

Planning to do something similar for Thunderbird as well, as it suffers from the same problem?

Because the article mentions that Chromium doesnt have HighDPI support right now: You can actually compile it with the -Denable_hidpi=1 flag which at least displays most web sites in the right way though the menu/navigation is broken (which is probably the main reason it isnt enabled by default).