Are there many users of PRADO out there? [closed]

Question

After making some comments, I've been inspired to get some feedback on the PHP MVC framework PRADO. I've been using it for over a year now and I've very much enjoyed working with it, however I notice that throughout Stack Overflow, it doesn't seem to rate a mention when symfony or CakePHP are being talked about as potential candidates for a framework.

Is anybody using Stack Overflow using PRADO now? If so, how do you find it? Has anyone used it in the past but left it behind, and if so, why? Can anybody appraise its strengths and weaknesses against Cake or symfony?

Answer 1

The first time I looked into PRADO, I spent about 10 days using it and kept saying to myself: "This framework is amazing!". A couple of months later, I started working on a big project where the customer had chosen to use PRADO... And Hell began... As long as we kept using PRADO's base components, everything was perfect and development was fast. But as soon as the customer wanted an out-of-the-box thing, we literaly spent 2 to 3 times the amount of time we would have done it with another framework. And I'm not talking about big customizations. The PRADO framework forces the application to have a particular structure and workflow. If that logic is not working for you, then check out another framework.

Answer 2

I've played with PRADO some, but I felt that if I'm going to be forced into post-back-hell i might as well do it on the platform that it was built for in the beginning - .NET, other then that PRADO is relatively "untalked" about in the blogs, etc. I don't know why really though.

Answer 3

I found that the active controls were pretty slick. It makes doing all kinds of ajaxy things really easy. Unfortunately, when you need to do something slightly different, it's pretty obfuscated and difficult to figure out what's up. I felt like I often got something simple and great working, and then one small additional requirement would require me to tear the whole thing apart and come up with a much more complicated solution.

Answer 4

Prado is dead now. Also the documentation is poor.

Answer 5

I think Prado never really caught on because it's an event-driven framework, which is a bit hard to wrap your head around. Especially for the many PHP developers coming from a more procedural background.

Answer 6

PRADO would have been my choice for a framework if I hadn't run across QCodo. I like the event-driven approach -- QCodo just suits me more.

Answer 7

We are working with PRADO framework since 4 years. We are developing huge (+4000 programs) web apps for e-Goverment with Oraracle and MySql databases containing more than 60 millon records. As infrastructure for development we use SVN+TRAC+ our own tools for project control AND phpEdit w/tortoiseSVN as client tools. Currently we are thinking on changing to Yii.