Torch VS bypass-finals

Torch is the proof that it's tightly coupled. Why do you even need a repo to show how to do it? Symfony doesn't have this issue. Just look at how much crap you need to wire to use a simple validation component: https://github.com/mattstauffer/Torch/blob/master/components/validation/index.php, it's garbage.

Other than the big frameworks, you could look at using Slim and other libraries/Symfony components to build your own framework - you could even use some Laravel components too.

You can check out https://github.com/mattstauffer/Torch to see them in action

This is was game changer for me: https://github.com/mattstauffer/Torch

Interesting! I actually found an example here: https://github.com/mattstauffer/Torch/tree/master/components/view

I had this issue when working with Dibi as I needed to mock final methods. You can use this https://github.com/dg/bypass-finals package and forget all the debate about finals against non-final.

It definitely is my job. If you feel you should ignore best practices and author's opinion, use something like this: https://github.com/dg/bypass-finals

Even with the keyword final it's still possible to extend by using the final disable library https://github.com/dg/bypass-finals but the fact you needed to disable it makes it very clear that it's unsupported behaviour.