Show HN: A PHP framework born in 2016 | Hacker News Reader

Show HN: A PHP framework born in 2016

bearframework.com

3 pointsivopetkov8 comments

Here is another thing that is different from many other frameworks. The Bear Framework API is designed, so you don't write all the time "vendor\", "Vendor::", "use vendor\" and so on. You write "$app->assets->getUrl()", or "$app->data->get()" and we believe this makes your app much more personal. You might even forget that you are using Bear Framework :)

The goal of Bear Framework is to help you start your next web project in less than a minute and help you make it successful. You've got routing, data storage, addons, logging, assets helpers and many more useful tools.

The documentation is available at http://bearframework.com/documentation/

Why should someone use this over any other framework? And why aren't you using all the PSR standards?

Here are some benefits: - Lighter than most other frameworks (including the so-called micro framework). It's about 40 files. - Fast and memory efficient. There will be benchmarks soon. - Simple API. Perfect for newbies. - Fast installation - just download and run. No installers. - Addons support. - File-based object storage for quick start. - Some nice utilities for assets.

Some PSR standards are taken into account, but not all of them. The goal is to provide simple to use and extendable framework that helps you do projects of any size.

Following PSR standards doesn't make a framework less simple, and it has the benefit of making lots of middleware instantly usable by that framework.

Number of files isn't a useful metric because other microframeworks can be run without ever loading the router or any of the data storage classes. They could be run with less than 10 files loaded. And even then, it still doesn't matter because number of files just means number of classes, which doesn't say anything about the readability or simplicity of the code.

Don't get me wrong. I think PSR standards are great, just not all of the fit into this framework. In PSR-7, for instance, Request and Response objects are immutable. Imagine the framework when this concept is applied to other objects. It will be a much different beast.

I've never felt that using an app like model for websites was a good idea. Maybe for web services but the website itself, if I have a page for say news. I want it to be self contained... and using shared code libraries...

Not sure what you mean. Can you give us an example.

Reply on news.ycombinator.com