The advantage to being 100% standards compliant would be that when you use a specific <insert technology here> feature, it would work as the <insert technology

The advantage to being 100% standards compliant would be that when you use a specific <insert technology here> feature, it would work as the <insert technology creator here> claims that it should. As far as why benefit to creating a browser in 2018 that targets 16 year old OSs, because there is no guarantee that we will be in a 64-bit (or greater) exclusive world by then. Without knowing the future, my goal setting off would to remain as cross-system ready as possible, which of course includes some 32-bit OSs