Hacker News Reader

Comment by bratao | Hacker News Reader

Ww also have a modern framework for php. Everyone should try http://laravel.com/ , such a fresh air into php development.

View on HN

What about phalcon (http://phalconphp.com/)? Which reminds me of two things:

[] TechEmpower Benchmark Round 6 was due today, but it was re-scheduled to the 25th [] Symfony should remove High Performance from their homepage title.

Phalcon is well done. I've been going through it recently and it will become my preferred mini-framework of choice.

Or at the very least just learn how to use Composer.

Agreed! Framework arguments aside, learn how to use Composer. If you haven't played with namespaces, this is a great way to start learning more about them and using them in your own codebase. It also makes it incredibly easy to work with other packages[1]!

[1] https://packagist.org/

We just implemented an internal composer repository for sharing code between our different services. I am surprised composer isn't more popular. I have been developing for a long time and have only recently heard of it.

React (http://reactphp.org) is nice if you want to do real-time or websocket stuff. Also supports asynchronous Redis, ZeroMQ, and DNS queries.

I would love to see an asynchronous database client (for instance Mysql) for it, but for now I use PDO.

Silex is better , i hate all these static classes everywhere. That's the only reason i'm not using Laravel "Core" . Eloquent is nice though.

Hmm, every new framework nowadays seems to be based on Symfony2 which appears to be kind of slow.

Is there any small (relatively new) PHP framework that isn't based on Symfony2?

probably not what you're looking for but maybe slim framework? http://www.slimframework.com/

4bytes is crazy fast: https://github.com/donutdan4114/4bytes-framework

Silex and Laravel don't really serve the same purpose. I think both have merits, and it's hard to say a micro-framework like Silex is "better" than a full-featured framework like Laravel, unless you're applying a specific context..

No static classes, they are facades.

I have mixed feelings about Laravel's use of the facade pattern. On one hand it brings a really simple API, which is great for new users and rapid development. On the other hand, it's hiding away dependencies and making testing slightly more complex. It's seems a bit like hiding behind multiple global service locators.

Reply on news.ycombinator.com