I don’t know what type of website you manage where you would even consider blocking chrome, that’s unfortunately roughly 65% of traffic, 70% if you include edge.
Maybe your site is for a niche group of people who mostly Firefox users? I’m just very surprised that’s an option for you as unfortunately chrome is what most people use.
—-
Anyway It looks like you can add headers in your server response to opt out of the calculation.
https://developer.chrome.com/docs/privacy-sandbox/topics/#site-opt-out
It shouldn’t hurt at all IMO
It’s still a very mature framework, works with client side apps via DRF if that’s your thing, and has only gotten more quality of life improvements.
There’s things to be desired especially with async but IMO old != bad
Also the last one is “learn python” which… Django is python…