Comments on: AMO Development Changes in 2010

By: Stephen Rivers

Stephen Rivers — Fri, 13 Aug 2010 10:17:01 +0000

Of course, it’s a great framework. I trieds a few months ago, but I have a problem with python (I simply don’t like it) so I gave up. But there are plenty of other good frameworks availlable, for PHP (Symfony and Zend being the best choices IMHO) and other languages (of course Rails, but less known but still powerful tools like Grails for Groovy, Catalyst for Perl), so I wanted to know if the choice was actually a matter of taste (or maybe a few developers who already know Django), or it came after looking for pros and cons of every other choice

By: Webdesign Köln

Webdesign Köln — Sun, 08 Aug 2010 23:28:34 +0000

CakePHP 1.2+ containable behavior + object oriented database results is amazing. Sounds like your programmers jumped the gun and chose not to learn how to maximize your development in Cake. Sad.

By: Joe

Joe — Sun, 01 Aug 2010 01:43:15 +0000

Why all the attention on porting from one platform to another? If the project has out grown one system and a shift is inevitable then all you can do is ensure that when you choose the next platform that it is going to be inline with your growth/development needs.

By: corre@ webbshop

corre@ webbshop — Sun, 25 Jul 2010 19:03:16 +0000

I think the change from cakephp to django is for the better. Anyway keep up the good work!

By: Traces of a new AMO « Mozilla Add-ons Blog

Traces of a new AMO « Mozilla Add-ons Blog — Fri, 07 May 2010 21:46:16 +0000

[...] have been reported sightings of the newly rewritten AMO homepage and add-on details page in the wild since yesterday afternoon. There’s a 15% [...]

By: All Night Diner : Continuous Integration comes to AMO

All Night Diner : Continuous Integration comes to AMO — Wed, 07 Apr 2010 14:54:16 +0000

[...] time to hail another milestone for AMO in our epic push for improvements in 2010. This time I’m happy to announce our Hudson continuous integration server which has been [...]

By: All Night Diner : Maintaining localization between Python and PHP (it’s not fun)

Mon, 08 Mar 2010 22:42:02 +0000

[...] reached my hand into the barrel of problems our migration to Python is going to cause and came up with Localization. It [...]

By: SUMO Blog » Blog Archive » The Evolution of SUMO

SUMO Blog » Blog Archive » The Evolution of SUMO — Wed, 24 Feb 2010 00:28:42 +0000

[...] entry to SUMO development, and hopefully make useful code available to other projects. Wil Clouser listed more strengths of Django as a platform when the AMO team decided to [...]

By: The Evolution of SUMO | Coffee on the Keyboard

The Evolution of SUMO | Coffee on the Keyboard — Tue, 23 Feb 2010 22:39:26 +0000

[...] entry to SUMO development, and hopefully make useful code available to other projects. Wil Clouser listed more strengths of Django as a platform when the AMO team decided to [...]

By: MongoDB / NoSQL for Web Applications | fredericiana

MongoDB / NoSQL for Web Applications | fredericiana — Wed, 17 Feb 2010 11:17:09 +0000

[...] cycle than traditional applications (an observation, for example reflected in the recent development changes on AMO). With all feature changes, related database changes have to be applied equally as frequently, [...]