No I did ’t. It ould e e t e el foolish to build a framework absolutely from scratch without recourse to some of the open-sourced tools and libraries out there. Leveraging the work of others is not new in software development so I used it. Nothing can ever truly stand without relying on other things!
with a very simple abstraction layer, a simple programming and tooling interface (simple is better) 2. Collapse boilerplate code for most commonly used libraries/services into one-liners (saves time and effort). 3. Help out with client-side technologies that need server-side o- ope atio e.g. Service-Workers, Content-Security-Policies, Application-Cache, Push/Desktop Notifications, Event-Source web- friendly media file, manifest JSON for web applications) 4. B i g do u e tatio to the de elope s’ pla e offli e do s a aila ilit 5. Create a basis for alternatives for very MUST-DO implementations for application features (variety makes things nicer). 6. Help out with basic Dev-Ops. 7. Help bring down the cost of deployment.
MVC framework just like Yii, Symphony, CakePHP, Laravel, CodeIgniter e.t.c and certainly not about the usual jollof rice. Se o dl , It’s has a o ept uite diffe e t f o the rest (though it copied a lot from Laravel framework) and is really easy to setup. It also employs minimal abstraction overhead so your apps load up and are served faster. Lastly, it plays nice with the ecosystem of open-sourced tools. It also abstracts away most of the boilerplate code for popular services like BugSnag, Auth0, AWS S3, Pusher, Mailgun, RedisCloud e.t.c.
2.Support for Faker.ng API within a Console command 3.Support for ReactJS server-side rendering 4.Support for Secure Headers & Database Migrations 5.Support for a more Robust Query Builder for database querying 6.Support for more package managers e.g. Bower and Yarn 7.Support for Angolia Search and BugSnag Error Reporting 8.Support for adding custom Console commands and custom Validation rules.