Define Roadmap for PIMF v2.0.0
Hello folks,
Garret asked me to create this chat in order to be able to create the roadmap for PIMF v2.0.0
From the beginning, there some features where we intentionally do not want to implement in PIMF, like:
- Queues & Tasks (better use Beanstalkd or Gearman)
- Mailer (please take a look at GitHub.com)
- ORM (heads over Doctrine, RedBeanPHP or Propel)
- Form Builder (come on, do we really need it?)
- Authentication, ACL (better find one at PEAR, GitHub or Composer)
- T9N, L10N, I18N, Math, RSS and much more (please search at internet, there are a tons of proven extensions and libraries)
- Dependency Injection Containers (nice OOP pattern, but in most cases complex and will push PIMF to full-stack framework)
Reason for that decision is, that we want still stay focused to keep PIMF being a micro framework, and there are features that do not have to be reinvented.
Anyway, I hope you are not scared of that :-)
Now I will present you some possible features for PIMF v.20.0:
- Incorporate modern features of the PHP language into the code base (Garret)
- Check if composer autoloader is available and implement it by bootstrapping
- Correction of spelling and grammar on the book-manuscript
- Correction of spelling and grammar on all PIMF quick-start bundles
- Test and fix all quick-start bundles with PIMF v2.0.0
From my side that's about enough for v2.0.0
If you have any other ideas for features or improvements, then please write them here ... and we will try to prioritize as good as possible.
Thanks a lot, I look forward to your feedback :-)
I am about to start working on my own full-stack framework, but as a micro framework I think PIMF has promise. If we can keep it running fast while improving the code structure, version 2 will be great.
I like the idea of using a DIC, but I can understand why you think it's not a good fit. Can you tell me what DIC packages you like? That may help me understand how it would complicate things.
- Yadif DIC (https://github.com/tsmckelvey/yadif)
- Symfony’s DIC
- But anyway. If you want to make improvements in the OOP area of PIMF, please feel free do it. And if you are thinking that implementing some lightweight DIC (or better some kind of “ Inversion-Of-Control paradigm”) will make PIMF faster, also feel free to do it. After that it will be helpful if we can see some benchmark results like PIMF-before vs. PIMF-after DIC implementation.
I have been working with an IoC container called Dice for some time (https://github.com/Level-2/Dice) and it is quite fast. I don't think any DIC will actually improve speed, but the best one would make development easier while being lightweight so as to not slow things down.
https://www.sitepoint.com/php-dependency-injection-container-performance-benchmarks/
Update forked PIMF Git repository
If you want to update your own fork of a repo with some repos upstream,than you should be able to clone your repo, add a new remote as upstream,
then merge your master with the upstream master.
# upstream is the name which you give to the remote
git remote add upstream git@github.com:gjerokrsteski/pimf-framework.git
git fetch upstream
# prefer using "git rebase upstream/master master" in order to avoid a merge commit if possible
git merge upstream/master master
git push origin masterpush)