Laravel uses Vue in most (if not all) of their own UI components, so it is a more "natural" fit than Angular. I haven't worked much with Angular, but I will agree with the sentiment that it is often too over-engineered for many tasks. That's perfectly fine; it is a framework created explicitly for SPAs, but it does introduce a lot of overhead that may not be worth it for small-to-medium size projects. Vue, on the other hand, really shines with its component-based approach and single-file views. While Angular starts with the assumption that it is the entirety of your front-end, Vue comes in assuming it is just part of your front end and leaves the rest alone, while providing facilities if you do want it to be your entire front end. The fact that it's written in pure ES6 may also be a selling point for Vue, and you don't actually need any build process like Webpack for it to work, unlike Angular and Typescript.
Laravel uses Vue in most (if not all) of their own UI components, so it is a more "natural" fit than Angular. I haven't worked much with Angular, but I will agree with the sentiment that it is often too over-engineered for many tasks. That's perfectly fine; it is a framework created explicitly for SPAs, but it does introduce a lot of overhead that may not be worth it for small-to-medium size projects. Vue, on the other hand, really shines with its component-based approach and single-file views. While Angular starts with the assumption that it is the entirety of your front-end, Vue comes in assuming it is just part of your front end and leaves the rest alone, while providing facilities if you do want it to be your entire front end. The fact that it's written in pure ES6 may also be a selling point for Vue, and you don't actually need any build process like Webpack for it to work, unlike Angular and Typescript.
Thank you and well done.