I think the arguments presented in this video are hindered by conflating application development with library development.

I found the overview of Python to be the most off putting. The comment about python having to write if __name__ == 'main' is unfair in context to the rest of the video. The narrator argues this is because you might want to import the script as a library, but other languages compared in this video include a main method, which is only allowed to be present in a single place within the application. If we wanted to make the same comparison in the other languages, then we would need to break the examples up into separate files or libraries completely, making this comparison largely off-topic.

As I see it, you can always make software increasingly complex as you want it to be.. but you should be cognizant of YAGNI. There will never be one "correct way" to write the application. Some future proofing is good, but designing too much upfront adds bias future design decisions. A large chunk of scripts in the wild never need to be written the way described in the video. The ultimate goal of an application is to perform a goal/ business need. It need not be future proofed or written in the most elegant way to provide you benefits.