Not only is this poorly written, but it's poorly researched. While I'm primarily a PHP developer, I take no offence to your post - but I thought it was worth pointing a few things out.

It would appear you dislike PHP (based on your most recent article) - would it not be more productive to write about the languages you prefer to work with instead, and how they benefit you?

You've tarnished Laravel with a negative brush but your opening sentence suggests all frameworks with a design pattern like Laravel are bad. PHP has Composer, Ruby has Gems, JS has npm/yarn, Perl (remember that?) has CPAN. Ironically, the concept of Composer was in use with Perl long before Composer was a thing.

When I came to the Blade heading, the first thing I thought was "Smarty". Yes you've covered it, but you've also highlighted that it's practically disappeared. The thing is (perfect quote from the Matrix), "there are some things in this world that will never change. Some things do change." The world has moved on, BASIC was once a very popular language but where is it now?

I think what you may actually be getting at is that these frameworks may take away knowledge and ability by doing things for you (reference to your last paragraph.) If that's the case, I share the same concern - and I would agree. Know the language well. Frameworks are there to assist, but cannot replace in-depth knowledge of any language. For a small project where I just need to do a handful of things I'll go vanilla. For a large complex web application I'll take a framework over vanilla any day.