How to justify the choice of technology stack?

Question

PHP

At the defense of the diploma, there will most likely be such a question as to why I chose these particular technologies.
I have pure JS and PHP with Laravel framework. The real reason is because apart from them I don’t understand anything (and I don’t understand them either). But this, like "more documentation than others / more popular", as an argument does not fit.
So, how can you justify choosing pure JS for the front, and not with a framework like Vue/React there? Well, PHP with a backend framework. For 3-4 sentences, briefly so that they can no longer dig into this.

Answer 1

I have pure JS and PHP with Laravel framework.

Firstly, it is not known how much code and what functionality you have in the project. Naturally, the tool is chosen for the task, and not vice versa.
If you don't have huge functionality for manipulating DOM on the frontend, this is not a SPA and it makes no sense to pull 10 more libraries for the sake of 200 lines of code - pure js is the best choice. Pros - well maintained, any mid-level specialist can support, no need for additional libraries that lead to additional dependency on someone else's codebase, no need to keep track of the latest changes in someone else's library, no extra files are pulled.
On the backend, Laravel covers well 90% of typical "sparkle" tasks, a wide selection of sufficiently high-quality modules for any sneeze, good test coverage, an extensive community and high-quality documentation. The quality of the code will definitely be higher compared to a novice coder if you use code that has already been written and repeatedly tested by someone. In addition, it has a codestyle, it teaches you to (relatively) a qualitative approach to development...
Which of these is applicable in your case - xs, since these are more general words, although they reflect reality well.

Answer 2

It’s hard for Laravel to justify
about js frameworks for many articles and on habré that they are a bad choice
on the backend, you should have done the same in a pure language plus sqlite,
and here you have a contradiction,
you did the right thing on the client, but blunted on the backend