Well, I have a pretty good github profile https://github.com/apsdehal but I still had a hard time finding intern this year. So I would say most of the github profile doesn't matter much, but it sure makes you look impressive. Also as far as I have experienced, if you apply in big companies, nothing matters for internship, only thing you should know is competitive programming.
Having a quick scan of your Github profile it looks like a lot of lists or collections of things or forks. I think you may be suffering from information overload as I was unable to find a decent example of code within 30 or so seconds
I apologize, we received a lot of intern applications and we are really just starting the intern search. We will get to yours for sure and send you a response. Or you can just send me an email at skhalsa@climate.com and we can go from there.
Check whats your need, if you are building up much bigger apps go for a fully fledged framework, rest for small apps you can use microrouters , according to your need, each has its own unique features.
One of the benefits of using a url router is access control - you could have a problem with just letting every file be executable by url, especially if you happen to have a remote file inclusion issue anywhere. With a router you know explicitly what can get invoked and what can't.
Although, doing it without a router is probably always going to be faster.
A late trick I discovered, was that you can configure your php instance to inclued a file with every script. For example the following can be added to .htaccess:
php_value auto_prepend_file 'before.php'
You can then use that for bootstrapping, front controller and to limit access. Can be a bit clumsy, but it's nicely divorced from simple page controllers.
I personally would still prefer a router but I know of a project which was written almost entirely in sprawling, procedural PHP that might benefit from this. Although I do wonder what the performance hit would be.
Good luck! Another feature of my router is that the method name converts snake_case to camelCase, so that resource/list_actions calls ResourceController::listActions(), but some of the features I mention will most likely incur a performance hit, but it shouldn't be significant once opcache comes into play
