I want to code for Oculus Rift and have full access to Facebook API from my program. It's a bit of a jump in the deep for me but that doesn't matter. I have some programming knowledge and will learn whatever I need to learn.
Right now for the above mentioned combination I'm thinking:
C++ with maybe OGRE plus the Oculus API (0.3.1 preview)
Use the Facebook PHP SDK (can be called from C++ from what I've read)
Please advise me on a sensible combination of languages/libraries.
Yes there is probably more than one way to skin this cat, but I have a feeling there is a more obvious way to a seasoned programmer: that's what I'm looking for.
Additional notes:
I'm not going to be making a 3D game, so I'm ruling out Unity.
I don't know what I'll be making yet (!) but I hope that it will be fun and that it will make use of the Rift together with FB to create something innovative.
I've pre-ordered the DK2
This question largely depends on what you or any particular person faced with the problem finds it easiest to work with. If I were working on this I would probably start with the Spring Social framework and the JOVR Java bindings for the Oculus SDK, for the simple reason that my familiarity with the toolset (I've worked with Spring extensively in the past and I wrote the JOVR bindings and examples) would let me get a prototype on which I could iterate up and running, probably in a matter of hours. On the other hand if you're not familiar with Java, Maven, Spring, or the Oculus SDK, it could take days or weeks of fighting code and figuring out the basic workflow just to get started on either the Facebook or Oculus integration sides.
I would suggest that you evaluate working with tools for Oculus tools for working with Facebook independently before you settle on your combination. Write a simple example to access the Facebook graph API in a language and then try to write a example of a simple VR scene in the same language. You may find that just because Language X makes one easy, it might make the other 10 times harder than it should be. Once you've tried that out in a number of languages / with a number of libraries, you'll be in a much better position to decide for yourself which combination will present the path of least resistance given your own skills.
Bear in mind that Oculus integration is probably the more limited of the two. There are bindings that I know of for C, C++, Python, Java and I believe C#. You can even use Javascript if you want to navigate the currently turbulent waters of WebVR. This may sound like an abundance of choices, but if you have zero experience and zero desire to gain experience in some of these, then you can probably strike them off your list pretty quickly.
Facebook on the other hand has far too many possible bindings to list them all here, and ultimately if you need to you can always work directly with the REST API, since in the end all of the SDKs are basically wrappers around network requests anyway.
I have been developing web apps (primarily) using php and a bit of python, mysql, etc for many years now. I have a reasonably good grasp of objective-based development, and use objects as much as possible in my projects, although I certainly don't take full advantage of them. I am comfortable enough to be dangerous with C++,C, and have even touched a bit on ruby.
All that said, Objective C is giving me a very hard time. Not sure if it's the syntax, the file structure, etc, but i'm just not grasping how to properly put together the different components of an app, despite having gone through a few tutorials and explanations online. I have xcode, and have tried doing some basic stuff, but get lost quickly in real implementation.
My question: Can anyone recommend me a really solid book/books with some good examples that I can walk through to help me understand this language better? I am primarily interested in database interaction (or xml parsing) and audio streaming/delivery capabilities.
Any suggestions would be very much appreciated! Thanks!
3 items:
The syntax isn't going to be a problem for long. Just keep reading Objective C code, and pretty soon the brackets will start seeming as familiar as the dots (or other forms of punctuation abuse) in other OO languages.
If you are a procedural language coder, you will have to get your head around event driven application design. The basic idea is you can't always tell the OS what to do, when you want to do it, and then do the next thing. You have to learn to chop up your procedural code into callbacks, and then let the OS call your code when the OS is good and ready. You might have to learn how to save appropriate state between callbacks (e.g. You can't use a "loop index" between callbacks without saving it somewhere.)
You might also have to get used to the object oriented MVC design pattern. It's like figuring out the difference between writing procedures for a one-man store, and setting up operations for a larger business with divisions in separate buildings. The guy talking to the customer isn't the guy closing the books. Same with MVC, the view presenting the UI to the user isn't necessarily the same object that does the storing or updating of the data representing what the user sees or does. Once you learn the logic of the separation, figuring out which file to look in for something will get a little easier.
I found Aaron Hillegass' book really helpful in learning Objective-C
iPhone Programming Big Nerd Ranch Guide
There are a bunch of good chapters that walk you through creating your own apps you can deploy right to your iPhone/iPad or run in the simulator. He explains some of the heavier concepts i.e. Core Data really well.
Other than that the Apple Developer docs are a great and invaluable resource.
I cannot recommend any books (I have learned it by doing a lot of experiments), but if you want to get started with Objective-C, I would recommend knowing what pointers are and how to use them. They form the most basic part of Objective-C and once you understand these (and NSObject), you understand 50% of the language itself.
You could, of course, read Apple's documentation at http://developer.apple.com/library/ios/#referencelibrary/GettingStarted/Learning_Objective-C_A_Primer/
I would recommend:
iPhone Programming: The Big Nerd Ranch Guide
It is a very nice getting started guide for both Objective-C and iOS programming.
The official documentation is great: http://developer.apple.com/library/ios/#navigation/
This is a great book. You need to understand Objective-C before you start jumping into creating apps (Cocoa Touch): http://www.amazon.com/Programming-Objective-C-2-0-Developers-Library/dp/0321711394/ref=sr_1_2?s=books&ie=UTF8&qid=1296848502&sr=1-2
This is a great intermediate book: http://www.amazon.com/Cocoa-Design-Patterns-Erik-Buck/dp/0321535022/ref=sr_1_1?ie=UTF8&qid=1292262048&sr=8-1
This is a great forum to learn stuff, in addition, obviously, to here: http://www.iphonedevsdk.com/forum/
The Apple developer videos are also great, and you can download them with iTunes if you want, to have them on the go: http://developer.apple.com/videos/
Also, check out the Stanford iPhone Programming Class videos on iTunes.
EDIT:
Here is the docs on Apple's XML class, NSXML: http://developer.apple.com/library/mac/#documentation/Cocoa/Reference/Foundation/Classes/NSXMLDocument_Class/Reference/Reference.html
And if you're going to be using databases, they'll probably be SQLite, and you'll definitely want to check out this wrapper for SQLite: https://github.com/ccgus/fmdb
I am in a partnership with someone. We are currently planning a system that can either use ASP.NET MVC or PHP With //Insert your framework here//. At this stage I can't say to much. Now the thing is I have a bit of experience with C# and MVC. I understand the concepts and actually wrote a fully functional blog with it. Now the other side of me wants to take PHP for a test drive. Will I waste my time? How good will ASP.NET MVC scale against PHP? I have to say that I love visual studio and the integration of MVC tools like quickly adding a view and a controller... Everything fits nicely. But the learning curve was quite steep and still is. I haven't really touched AJAX and Jquery yet but how easy is it to use it with ASP.NET MVC? I already googled and researched this but I want opinions of those who have been working with these technologies.
Whats your guy's opinion on this? Should I stay with .net?
Regards
RaVen
You don't give any deadlines. If you have time look at PHP. Remember if you use a framework you need to eventually understand that framework if you're going to use it for anything long term or critical. You can barely do any PHP but you can throw up a site quickly with PHP, it might not be the best thing, again, unless you have time.
If you know ASP.NET and you don't have time or the inclination/passion to learn something new (a new language that is), then don't waste time with it. Use what you know. Make money with it so you can eat.
At least with your knowledge of MVC you can start learning the Ajax and Jquery stuff immediately.
What does your partner know how to do?
I developed in PHP for years and now develop in ASP.Net/MVC2 and wouldn't go back for a whole chunk of cash
It's possible to program elegant, efficient code in PHP but it takes a whole lot of work and discipline - .Net makes it a breeze.
I also find that I find more problems at design time as opposed to run time using .Net thanks to the background compilation and strong typing.
Once you get big enough, TFS is a fantastic source control system (especially if you can get it free via BizSpark). I know svn/similar are also good but personally, I find TFS feels far more "complete".
In summary, I loved PHP but it was just too much work to write good code quickly. With .Net/MVC you'll be ahead as long as you start with a good architecture.
Yes, you should stay with .Net
You may want to use the new Razor view engine and ASP.Net MVC 3, which are currently in RC status.
It allows you to make much cleaner views.
In general, stay with what you know.
But, PHP is more than capable of matching .net. Check out the CodeIgniter Framework. In my mind it is the PHP framework that most closely matches .net MVC 2.
I'm a PHP developer and love it, but I wouldn't convert from C# and .NET to PHP unless there is a really pressing reason.
If you're planning to grow fast, reasons for PHP could be personnel costs (it is said to be easier to hire PHP people, although in my experience, this is not necessarily true for the really good ones) and, more importantly, server costs. As a general rule, it is cheaper to get Linux/PHP based hosting.
I would say most definitely stay with .NET. This is what you are comfortable with it will be quite sometime till you get the same comfort level with PHP.
As for scalability .NET MVC scales much better than PHP. Stackoverflow is made with ASP.NET MVC. Digg is made with PHP. Here's what joel had to say about that : http://twitter.com/#!/spolsky/status/27244766467 (although the database plays a very vital role in this as well)
Now, given how new I am, I'm rather lost as to how I get started. Down the road, I want to use MVC framework so that I help myself be disciplined in the way I build. However, I know basic knowledge of PHP and OOP PHP are required. So my question is this: what are the right steps to mastering Cake PHP? I don't want to skip critical phases of learning before learning to Cake PHP. At the same time, I don't want to spend more time than required learning PHP if I can learn it directly through Cake PHP knowledge.
Any advice would be appreciated.
IMHO you should be comfortable writing at least a basic app in clean standard procedural code before using a framework. That means mastering all the basic elements of the language like if and switch, loops, functions, local and global variables, etc. It also includes being comfortable with HTTP GET and POST, RESTfulness and how to persist information between page loads (Cookies, Sessions, URL params). A basic idea of Javascript and AJAX would help as well.
Good exercises might include:
A page that outputs database contents and is paginatable, filterable and sortable by various fields.
A shop checkout process or similar "wizard"-like page.
That's when you can pick up a framework, since most frameworks abstract exactly these kinds of tedious things away from you. Especially Cake has a lot of automagic built in, which will leave you hopelessly confused if something goes wrong and you have no knowledge of the above mentioned. To start with OOP, you might want to try something like Zend first, which is a lot more transparent in how objects are used.
Deceze gives good advice, though I disagree that REST is a core concept for learning PHP. You can author a perfectly successful web app that isn't using the concept at all, and I don't think that you'd be hurt by learning it along with a framework.
The rest of his advice is good, however, and, so that you aren't out there on your own just crawling the web, I heartily recommend PHP and MySQL for Dynamic Websites by Larry Ulman. It won't teach you (much) about OOP, but it will give you a very solid foundation in PHP and MySQL, as well as how the two play together. More importantly, you'll cover a lot of core programming concepts applied to practical examples in PHP. This book was fundamental in my development as a programmer, providing baby steps and advanced techniques that made it a lot easier for me to digest more complex topics later on.
For a start, use the Cookbook
Although, I'd strongly suggest getting familiar with PHP itself first - any introductory level PHP book should suffice.
This one was by far the most useful for me
Build Your Own Database Driven Web Site Using PHP & MySQL, 4th Edition
http://www.sitepoint.com/books/phpmysql4/
It went through all the basics in a very logical way, and then challenged you to take some first steps on your own.
After reading this book, I'm at the same point. Whats the next step to understanding OOP, and implementing a framework like Cakephp...
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am wondering why this framework (QCodo) is almost forgotten and totally unpopular.
I've started using it a few years ago and it is the only thing that keeps me with PHP. Yeah ... its development is stuck (that's why there is now more active branch Qcubed) but it is still very good piece of software.
Its main advantages:
Event driven (something like asp.net) no spaghetti code
Powerful code generation
good ORM
follows DRY
very simple AJAX support
is fun to write
Since then I wanted to be trendy and checked Django but I cannot write normal request-based web application (it just doesn't feel right).
Don't believe? chess.com is written with it and surely there are plenty others.
My 2 questions are:
Have you heard of it (PHP people)?
If you are using it what is your opinion about it (show us examples of your work)
Thanks
I've used PHP a lot for many years and never heard of it.
The creator(s) of Qcodo never really promoted the framework, and thus, didn't generate a large following. I believe they created it mostly for their own use, but also offered it up to others. It is awesome if you are looking for a code-generating framework. It does have a learning curve. So to get the most use of it, it's best to spend time studying the examples.
Qcodo has really had no active development for well over a year and there doesn't appear to be much chance that development will continue on Qcodo anytime soon. Qcodo appears to be dying a slow death.
Qcubed, a branch of Qcodo, is under active development and has been since Nov 2008. It was created by users of Qcodo who got frustrated with the lack of Qcodo progress. If you are just getting started, start here and not with Qcodo. But use Qcodo forums to search for problems/questions you may have.
Qcodo and Qcubed are fantastic frameworks. Don't discount or underestimate them just because you've not heard of them.
Emulating ASP.NET or Wicket in PHP is not a good thing to do. Moreover, the code style does not look good to me.
$this->btnSavePage = new QButton($this);
$this->btnSavePage->Text = "Save";
$this->btnSavePage->Visible = false;
$this->btnCancelEdit = new QButton($this);
$this->btnCancelEdit->Text = "Cancel";
$this->btnCancelEdit->Visible = false;
Hungarian notation? OMG. I need to create a big object to create a button? Heavy weight to me.
Yes, we do use it at Chess.com and overall have been very happy with it. It can get problematic trying to figure out how/where to store all those QFormStates when you're getting well over a million pageviews a day. Every page view is its own QFormState! We solved this by putting all of them into memcache! It does have a bit of a learning curve, but once you know it, you never really need documentation any more. I actually have moved away from using QQ entirely, and use all custom sql in our ORM files. QQ is just not powerful enough to do heavily optimized queries and highly tuned queries is more important than database abstraction. After all, the site needs to function and be fast. Here is one example ORM static method in our User class to load a random user from the database (we used to use this to show a random "user spotlight" on our members page). Notice how it uses the slave database, not our master (custom built function). It also uses memcache so that the randomized user only changes every 10 minutes (600s).
public static function LoadRandom($blnAvatarRequired = true, $blnForce = false) {
$strCacheKey = MyMemcache::QueryToKey("User->LoadRandom()");
if($blnForce || false === ($objUser = MyMemcache::G()->GetQuery($strCacheKey))) {
$objDatabase = QApplication::GetSlaveDbConnection();
$DaysAgo = new QDateTime(QDateTime::Now);
$DaysAgo->AddDays(-10); //make sure this is an active member
// Setup the SQL Query
$strAvatarReq = $blnAvatarRequired ? ' and u.has_avatar':'';
$strQuery = "
select
u.*
from
user u
where
u.is_enabled=1 and
u.create_date > '$DaysAgo'
$strAvatarReq
order by
rand()
limit
1
";
// Perform the Query and Instantiate the Result
$objDbResult = $objDatabase->Query($strQuery);
$objUser = User::InstantiateDbRow($objDbResult->GetNextRow());
MyMemcache::G()->SetQuery($strCacheKey, $objUser, null, 600);
}
return $objUser;
}
Qcubed and Qcodo are used by us in 3 projects and these ones are the cleanest and easiest to maintain projects we ever had! This is great stuff and easy to understand.
Just go into the code you won't need much manuals.
Qcubed community is much stronger at the moment so you might want to check in Qcodo forum for your answers on basic problems, but post on the Qcubed forum.
We will continue to stay with this fantastic product and community!
Regards,
tronics
http://www.twitter.com/qcodo
No, I'd never heard of it.
The main ones I've heard of are Zend, CakePHP, Symfony, Code Igniter, and one or two other ones I can't recall the names of right off the bat.
I've been doing PHP work on and off for about 3 years and have never heard of it. Ask anyone to name a PHP frameworks and you're gonna get the usual suspects: Code Igniter, Cake, Zend, etc.
Guess QCodo devs need to work on their marketing a bit!
I've been using QCodo for 2 years and now I'm with QCubed.
This is the nice way to develop and maintain web applications, as well as, the easiest way to deploy code and test it. Remember that QCubed is now growing in acceptance and it's good for all QCodo's Community.
I think that frameworks can save a lot of development time but it many cases it's not recommended for all yours web developments.
I started to use it two years ago. The pro:
code generation from the database
ORM object oriented
simple use of ajax
Cons:
qcubed community is not so skilled to carry on a project with new good ideas
the new code is not at the level of Mike Ho.
bugs in the state of qforms, the forms of qcodo/qcubed.
is not popular.
they do not want to go ahead and use DDD and forward engineering.
the forms only works with js enabled.
is written in PHP.
new plugin system poorly designed.
At the moment, Grails seems to be the best framework, very DDD oriented, with the possibility to use any existing Java code, good template library, possibility to use different js frameworks, built on Hibernate and Spring. With Grails is possible to write simple web app or financial application.
I hope not to use PHP in the future, but since I know Qcubed/Qcodo I will use it if it will be necessary. For newbies, I reccomend Symfony, bigger community, mre plugins, feature rich, it has a more secure future.
Updates:
No database migrations, no way to track database schema changes
No schema reflecting which tables are generated
It is not designed to real TDD, it is not easy to test models, controllers and views. They just added a testing framework to an unfriendly testing web framework
QForms still bugged and can loose status when using several controls and trigger Ajax error and blocking the application.
The ORM is very boring to use in the long term (lots of chatty/redundant code) and cannot be tested with a tool like Rails console, in the end it takes less time to use pure SQL and test it with phpMyAdmin.
Bugs in the ORM too, sometimes I get a string when I declared the field as integer (code-generated queries).
There is not a front controller and a routing system and the framework is inside the public path! The plug-ins are installed in the public path too!
Strange directory structure not similar to other MVC frameworks and they thing that the M stands for ORM only instead of model.
not link_to tag like Rails or Symfony and many other tags.
Over complex metacontrols that are useful to waste time only.
Framework focused in scaffolding when in Rails it is not used a lot since most of the developers use a user centric design instead of data centric one.
The views are full of object->render and JS and custom controls are a pain to be customized, and instead of staying inside a template are inside a class with logic session .. everything.
It does not work with PHP 5.3 (not tested but should be resolved) and on Quercus.
Rails/Grails has ton of plugin doing everything.
I could continue but I think you get the idea. Just learn Rails or Grails for few months then let me know what you think.
I am moving my Qcodo project to Rails and I have a wonderful environment, nice community and most of the innovation in the web is around Ruby and Rails. Rails has been voted several times as best web development tool and is the only one that can substitute Java or .net
While I have heard of it (Qcodo... not this fork) I never looked into using it. There are tons of frameworks and only so much need. PR and mindshare are hugely important in such a situation and Qcodo never really had either. Now that I am settled on a handful I have no time, nor inclination, to start learning a new framework.
This Swim Log uses it mySwimLog
I've been using QCodo since beta 2, and am now a core contributer of QCubed, so yes, I've heard of it.
What initially drew me to the framework was the code generation. I came from asp.net, and codesmith, and was very pleased to find a framework that gave me both the event-driven approach of asp.net and the code generation of codesmith.
I also love that it's all pure OO PHP, which means I don't have to learn a new language to develop my PHP app, and customizing any aspect of the framework that doesn't behave like I want is simple.
All of this has resulted in us being able to produce an easy to maintain and robust Learning Management System that we have sold to and host for numerous Fortune 500 companies.
There are some downsides, such as the runtime overhead of an ORM approach, but the readability and clean layout of the code results in the ability to more easily streamline other aspects of the application, and significantly reduces both development time, and the number of bugs produced.
Since QCubed is a community driven project, anyone is able to submit tickets, suggest improvements or discuss changes, it's very clear where the project is going, and very open to constructive feedback.
In defense of some of the negative things said here, I will simply point out that tickets for most of the supposed "problems" simply have never been created. And I would encourage anyone that does encounter any of them to please create a ticket for us to look at at http://qcu.be.
OK, Here is something I want to tell about this Qcodo / Qcubed thing:
Its brilliant. I just have no words about how great it is. You say CodeIgniter? Symfony? I say Qcubed.
It was when I wanted to start off the project I am working on and I looked into all those and through a Wikipedia article, landed on Qcodo site, and then on Qcubed...and I was surprised.
The features I loved the most:
No SQL queries needed. Of course, it can be done but most things are taken care of!
Speration of Templates from the core functionality.
Creating custom controls is a piece of CAKE (and its not CAKEPHP).
Totally Even driven. Saving states is like..."where does that happen?"
NO LEARNING CURVE. Just look at Yii or Symfony exmaples and then go for Qcubed examples. Its much simpler compared to others.
Full AJAX support. I love this.
No JavaScripting. Ask it to do something as a 'javascript' action, it is done by javascript. Change one word to 'QAjaxAction' and it goes to ajax. Change again, page reloads. What more do you want?
Autocomplete, typecasting (both automated and manual control) and what not!
Inline editing of almost anything!
yeah, there are a few cherries on the ice cream when it comes to Yii. But I think Qcodo has more inside.
You say Authentication support? Well, I created one to integrate with Qcubed in 1 day. It saved a week of lerning headaches with other frameworks. Qcubed rocks.
yes, I hate its slow development. But I think its near to complete! (may be I know too few things but anything I am capable of imagining seems to get solved through Qcubed).
I wish it was more popular...I would have saved me a week of search before landing on their pages.
I have used QCodo/QCubed for 1.5 years now. Started with my own framework, which at some point seemed messy. That's when I started looking for a more mature framework. Luckily I found QCodo. Since then I have never even considered looking for something else. The framework is so flexible and powerful, that you can do everything you want with it.
I had almost no experience with event-driven architecture. So, the beginning was somewhat hard, cause there was few documentation available. But community itself is very active and you probably get answer to your newbie questions in 1-2 days (sometimes even in hours). But currently the documentation level is way better and community is even more active :)
Nothing I can complain about. And if I have some problems/suggestions, I will try to discuss those with core developers. Whining about stuff without constructive discussion is lame imho.
I have used QCodo/QCubed for 3-4 successful projects now. The more I use it, the more I like it :) And also, I'm trying to help developing even better framework whenever I have spare time. And I can say, that I have had more than 10 people, who I have convinced to start using QC now ;) And I hope there will be many more.
QCubed totally rocks!
Never heard of it.
Been doing PHP on and off 4+ years
http://www.piranhamethod.com/2009/04/09/qcodoqcubed/
I have heard of it and I love it.
I also came from a dotNet / Codesmith environment. When I picked up a project that wanted to translate a dotNet site to PHP I looked for a framework that could best emulate the way the original application's logic was set up. What I found was either bloated frameworks or frameworks that did not completely fulfill the projects requirements.
I accidentally found QCodo while researching using the MyGeneration tool for PHP code generation. I have not looked back since. The ease of use, ability to quickly build complex applications and the true OO approach QCodo now QCubed uses makes it the best framework for my purposes.
I've been using QCodo, ZCodo and now QCubed for quite a while now.
I actually picked it as a replacement for CakePHP, which at the time of my need, wasn't mature enough to do the things I wanted.
I'm super happy with it as a framework; it abstracts things just enough, but not too much that you lose sight of the programming.
I plan on using it for any development project I'm responsible for in the future, and I'm looking forward to QCubed being the best community maintained framework for PHP5 out there.
The quick reason is that popularity and success do not generally go with what's technically best. I'm sure any techie can come up with numerous examples. There are numerous things that can promote mediocre solutions, like marketing, first-mover advantage, being a touch better in some area that catches people's attention, being used in some high-profile application, or just plain luck.
The other reason is that what appears technically best to you may not appear so to somebody who's doing something different.
I think that QCubed is great and mainly because of the way you can use Ajax (you dont have to write Jscript and you dont have to use jQuery).
One very useful document: http://www.qcodo.com/demos/QcodoClassLibrary.pdf
I chose QCodo 4 years ago to develop our product. I've never regretted - now we're 3 developpers on the thing, and any non-OOP solution wouldn't work. We have installed almost 50 customers with it - on Apache, IIS, my SQL and SQLServer platforms, Linux or W2003.
F
The design is brilliant, code-generation is great, and it's really easy to develop, extend, and maintain. I can't read any other code now...
Yes, marketing is quite poor, and the project used to depend just on the creator (Mike Ho). All of it moved to Git recently, and marketing should be better soon. And, now Mike Ho is back !!!
I have used it in few projects involving Flash remoting but I only use the ORM in the framework as I don't really like EDP stuffs like .NET. The flow doesn't seems right at all for stateless web. It's great if the ORM can be released as a separate component.
I never heard about it.
I didn't used it.
qcubed community is not so skilled to carry on a project with new good ideas
Nonsense
the new code is not at the level of Mike Ho.
Nonsense
bugs in the state of qforms, the forms of qcodo/qcubed.
??
is not popular.
So what
they do not want to go ahead and use DSL and forward engineering.
Your point? Every framework that doesn't want to go your route is wrong? I for one would not want the suggestions you have made
the forms only works with js enabled.
You have to be kidding right? If users don't have JS enabled, then they're in the stone age...
is written in PHP.
No comment
new plugin system poorly designed.
Based on what do you say that? I would say nonsense to this as well
Clearly there is some hidden agenda with this poster...I've also had a close look at Symphony - and I would go with QCubed over Symphony every single time. For big apps or small