A future without frameworks

Frameworks serve a purpose, but the further your application has to grow, the more frameworks "get in the way". In this talk I'll go through the evolution towards a service oriented architecture.

While frameworks allow us to quickly build an application while maintaining a consistent structure, marrying our entire codebase to a specific way of doing things may sometimes work against our own interests. This talk uses the Unix philosophy to propose a different approach.

Transcript

1. A future without frameworks Mariano Iglesias - @mgiglesias #PHPConfBr 2014
3. A story of how I got into PHP frameworks
4. From CGI with C, to Perl, to Java, to... PHP
5. $table = new table(); $table->openRow(); $table->addCell('I want to die'); $table->addCell(new image('delete.png')); $table->closeRow();
6. Just because you used classes, interfaces, and namespaces it doesn't mean it's not spaghetti #FACT
7. $ rm -rf /var/www
11. So it's all good... right?
12. “If I could create Symfony from scratch today, I'd do it totally different.” Fabien Potencier
13. “Our current ideas about frameworks are harming the industry.” Nate Abele
14. “MVC, MVVM, ADR, are all bad jokes. They solve the easy problem, and forget about the hard one.” Anthony Ferrara
15. “Frameworks? They all suck.” Rasmus Lerdorf
16. So something's going on...
19. If your framework did not get in the way, don't worry, it will (hopefully). #FACT
20. Your framework decision affects others … if you are successful
22. Hidden Complexity
23. Sendgrid Customer.io DB REST app
24.  Laravel: 273k lines, 0.19 complexity.  Silex + Doctrine: 109k lines, 0.19 complexity.  Slim + Illuminate (ORM): 42k lines, 0.15 complexity.  Slim + PDO: 21k lines, 0.13 complexity
25. It's more than just the # of lines
29. Now, there's this thing...
31.  Write programs that do one thing, and do it well.  Write programs to work together.  Write programs to handle text streams, because that is a universal interface. Doug McIlroy, inventor of the Unix pipe
34. The more your application grows, the more you'll want to break it into pieces (aka SOA) #FACT
36. Ok I'm sold. How do I get there?
37.  Use Gearman/RabbitMQ to implement worker queues.  Decoupling in code, and business logic.  Does it all have to be PHP? No, use the right tool for each job.
38. Focus on your own problems
40.  Look for a package in packagist.org  Found one but misses something? Collaborate.  Nothing there? Create (and submit) your own.
41. PHP The Right Way
44. Questions? Mariano Iglesias - @mgiglesias #PHPConfBr 2014