I actually covered this in my talk tonight. The requirement was that it should be transparent to end users. Our only tool to monitor success is traffic (we are not a paid site) so if a new feature or usability change improved or decreased traffic, we wouldn't know if the rewrite or this new change was the cause. There is also a brand issue. We have millions of loyal users and loyal users tend to love the "current" UI and that doesn't matter what site you are using.
Sorry for the late reply, I've been concentrating on the presentation. ~Eric On Tuesday, February 21, 2012 4:31:50 PM UTC-5, Andreas Schmidt wrote: > > Great news :-) I'm currently working hard on a complete rewrite of our > site. We don't have as many impressions as youporn has but I'm quite > interested in the challenges you overcame. I'm looking forward to your > report :-) > > By the way: what were the reasons for symfony2, and what was the reason > for the complete relaunch with changes only related to the backend, and > leaving the frontend as it is/was?! > > Greetz from germany... > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
