Password lists are full of weak passwords. You don't brute-force the password, you use a password list instead.
Potato, potato. Does anybody really say “bruteforce” not meaning a dictionary attack?
The author of the article, apparently.
Yes, plenty. It's not great for passwords, (but sometimes it still is! Sometimes sites using MD5 still get popped) but there's plenty of other problem spaces where brute forcing still means brute forcing.
Sorry, forgot to clarify! Yeah, the context matters here: if you’re cracking something like a numeric PIN, or looking for something like a hash collision, you might want to iterate through all possible solutions, randomly or sequentially.
Credentials stuffing. Attackers can spam a site with logins with common passwords. Too few sites implement good mitigations against this because it's easy to block/lock legitimate users that typoed a password.
This is why I isolate authentication to a separate application. I also implement max attempts per N minutes for IP and User. Most users once authenticated are good for the work day. Auth going down doesn't (generally) affect the work.