The new Joomla Framework was met with both skepticism and excitement in the community. What is the difference between the Platform and the Framework? Why is it a good idea? And how does this open us up to the wider PHP community? We'd like to give you some answers.
5. The good
Strong focus on unit testing and continuous
integration
Independent release cycle
More decoupled code
Higher code quality achieved
J!Oscar 2011
Innovation of the Year
6. The bad
Confusing version numbers
Hard to use our great libraries in non Joomla based
apps
All or nothing
Need to maintain a high level of backwards
compatibility
7. The ugly
Huge baggage of CMS specific code
if (class_exists('JError')) {
! return JError::raiseWarning(100, 'Unable to
read archive');
} else {
! throw new RuntimeException('Unable to read
archive');
}
26. application archive cache
client compat controller crypt
data database date event
filesystem filter form github
google http image input
keychain language log model
oauth2 profiler registry router
session string test uri utilities
view
28. Per-project dependency management
Public repository on packagist.org
Or host your own using Satis
Adopted by Symfony2, Laravel 4, Zend Framework
2, Drupal 8 and many more
Creates an automatic autoloader
36. Support YAML in Registry thanks to Symfony2’s
YAML
Considering to adopt Symfony2’s Session system
Dropped JMail in favor of using Swift Mailer or
PHPMailer
Monolog will probably be the recommended logger
37. Currently in alpha state
Expected release in Q4 2013
80% done - but the last 20% are the hardest
Need to fully decouple unit test
String package not ready
Need the Cache PSR
How far are we?