json.load(f) simplifies reading JSON from disk.

If you ever wondered why json.loads ends with a "s" it's because it's specifically for working on a string, but there is another related method: json.load

json.loads is for deserialising a string containing JSON, while json.load (no "s") is for deserialising a file containing JSON.

The methods are very related. In fact, json.load is a wrapper around json.loads. It's a method provided out of the box by Python to simplify the task of reading JSON from file-like objects.

Python core developers are very careful about what features are included in the Python builtin modules, so it makes sense to utilise the convenience methods and not reinvent the wheel? For example, these result in the same outcome:

with open('some/path.json', 'r') as f:
    content = json.load(f)

with open('some/path.json', 'r') as f:
    content = json.loads(f.read())

So why not choose the easiest to read, write, and execute (the first one)?