Consider a command like:
```
wp widget add rss sidebar-1 1 --url="https://wp-cli.org/feed/"
```
Historically, the `--url=<url>` parameter has been treated like a global
runtime argument, which has meant a command can't easily use it as its
own. Now, using the `WP_CLI_STRICT_ARGS_MODE` will tell WP-CLI to treat
any arguments before the command as global, and after the command as
local.
For instance:
```
WP_CLI_STRICT_ARGS_MODE=1 wp --url=wp.dev/site2 widget add rss sidebar-1 1
--url="https://wp-cli.org/feed/"
```
In this example, `--url=wp.dev/site2` is the global argument, setting
WP-CLI to run against 'site2' on a WP multisite install.
`--url="https://wp-cli.org/feed/"` is the local argument, setting the RSS
feed widget with the proper URL.
I've thought long and hard about making a breaking change, and enforcing
strict args mode by default. At this point, I don't think it will ever
be worth it, given the majority use case isn't impacted by it, and it's
a better user experience to be able to supply arguments in an ambigious
order. When you need to be strict, you can use the environment variable.