It does specifically say “defaulting to https:// if the site supports it”, so I think specifying http will still work if the site doesn’t actually support https.
It does specifically say “defaulting to https:// if the site supports it”, so I think specifying http will still work if the site doesn’t actually support https.
Also to add that “well known principles and approaches” doesn’t always equal good, readable, maintainable code; especially when it comes to a lot of OOP principles. Abstracting everything into a Factory/Decorator/whatever pattern you might think is the best approach after having only worked with OOP principles your whole career is almost always not what’s actually the best way to structure things. In fact the code OP is complaining about may not even be that bad, it might just look so to someone who has no familiarity with any programming practices (like FP) that are outside their bubble.
The iPhone’s portrait mode uses actual depth information captured from the separate depth sensor. The new feature is that it will always capture the depth information for every picture you take so that at a later point you can use it to blur parts of the image at different depths. Google’s version of portrait mode just uses image recognition to detect what’s in the background. It does a good job, but not as good as if it had actual depth information.