1,519 karma · joined May 7, 2012
The problem for me is working with a big legacy codebase. I'd rather have php break backwards compatibility and change === to ==.
Noticed "0.2" == "0.20" as another example
[1] https://www.php.net/manual/en/language.operators.comparison.... [2] https://www.php.net/manual/en/language.types.type-juggling.p...
I assume you will only be charged for full hd if the client is streaming it
Also it seems a lot cheaper, assuming full hd is 1 MB/s. That would mean approx 3.6GB/h which would come out at 0.54$/h in comparison to their 0.15$/h pricing
Another example of why you should never mess with the defaults unless strictly necessary.
"Due to adjusted work schedules at this time, we are currently experiencing longer than usual review times. Please expect review times of 7 days or longer."