#slive2010 Liveblogging: Fabien Potencier: Symfony 2.0
February 17th, 2010 by Tom 7 CommentsI am liveblogging Fabien Potencier’s Symfony 2.0 presentation. Bear with me and my editorial errors, simplifications and bare-faced libels.
My own opinions are in parentheses.
They are setting up now.
“Symfony 2.0 Reloaded” Preview Release
“I’ve decided to do the session in French” heh
In 10 minutes you will discover the shiny new version of Symfony, Symfony 2.0. Symfony 2 is just awesome. But first a bit of history.
Symfony 1.0 released in January 2007. Started as glue between existing libraries: Mojavi, Propel, Pardo i18n, …
“How many of you are still using 1.0?” [Some hands go up] “Ohhhhh!” [Hey, I raised my hand too, I have to support existing projects after all, heh. Our new stuff is all 1.4]
With Symfony 1.2 in November 2008, decoupled but cohesive components wre rolled out: forms, routing cache, YAML, ORMs… but still the same core.
Symfony 1.4 – November 2009. Added polish on existing features. Removed the support for deprecated features. Current LTS released, maintained until late 2012.
What is Symfony 2.0? The next version of course… except Symfony now takes an ‘S’ instead of an ’s’. That’s the big difference!
Talk about Symfony 2 with a capital S please! Symfony 1 (uppercase) does not make any sense, symfony 2 does not make sense! It’s all about Symfony 2. “I’m quite picky.”
“Same philosophy, just better.” We’ve learned a lot from our mistakes. We’ve learned a lot… we have problems with Symfony 1, but not all are fixable. It requires breaking backwards compatibility. So we need to go forward.
Symfony 2 is still an MVC framework.
It’s probably more of a Fabien-style framework than anything else (his words not mine (: ).
MTV: Model, Template and View?
Highly configurable and extensible. Same Symfony Components (DI, events, request, etc), same great developer tools, full featured.
Everything is upgraded to PHP 5.3. (Great, I hope they debug PHP 5.3 by the time Symfony 2.0 is complete!)
OK, but why a major version # change then?
(more…)



