A very small one, nonetheless. Anything you do that tries to avoid code duplicity will end up looking like a framework anyway. The point of frameworkless is not to avoid frameworks at all, but to make things simple and keep the code under your control, in order to be able to eliminate as much technical debt as possible. Which I believe is exactly what you want to do with your approach: keep things simple, stick to the basics.
But yeah, I guess I could strip some stuff from there and go even simpler, but then I wouldn't have a Router anymore. Sad. ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for commenting.
I like your approach, but isn't it a bit of a framework? ;)
A very small one, nonetheless. Anything you do that tries to avoid code duplicity will end up looking like a framework anyway. The point of frameworkless is not to avoid frameworks at all, but to make things simple and keep the code under your control, in order to be able to eliminate as much technical debt as possible. Which I believe is exactly what you want to do with your approach: keep things simple, stick to the basics.
But yeah, I guess I could strip some stuff from there and go even simpler, but then I wouldn't have a Router anymore. Sad. ;)