Skip to main content

Symfony 2 or Lithium?



The answer may be based on 4 aspects:





1.- simplicity: we all hate write tons of code for simple tasks like in java, this is the reason why we use php, importing design patterns from java/university world is good, but usually independent developers like me need dev speed more than enterprise employees.





2.- backend: how easy will be building a backend in symfony 2 vs lithium?. not always we build a facebook like project and we need our preferred framework to get the job done on little projects too.





3.- community and docs





4.- performance: scale good with the minimum



Source: Tips4all

Comments

  1. As the lead developer of Lithium, my answer is going to be a little biased, but I'll try to address each one of your points in brief:


    I believe the code required to write a Lithium app is simpler and more concise than the corresponding Symfony code would be. We favor more declarative, idiomatic code, and less configuration.
    Lithium scales down to small applications quite well, even very tiny ones. See the "Route Handlers" section of this post for an example of how to design a micro-app in a single file: http://dev.lithify.me/lithium/wiki/blog/Lithium-0-9-The-Lambdas-are-awesome-Edition
    Lithium has fairly comprehensive (and growing) API documentation (http://lithify.me/docs/), as well as a set of tutorials (http://dev.lithify.me/drafts/source/en) and various other documentation, which we are developing a portal to aggregate. Our community is small, but very solid and growing rapidly. Also, we're fortunate enough to have some very high-ranking members of the PHP community in our user base, including PHP documentation and core code contributors, and popular conference speakers, including these guys: http://analog.coop, these guys: http://fictivekin.com/ and the founder and former lead developer of the Joomla project.
    Lithium's core code is fairly well optimized, but the most important part about it is that it doesn't remove any choices from you about your application's performance. Because there is always a trade-off between performance and speed of development, Lithium allows you to get up and running quickly, but makes it easy to change how the framework operates in order to performance-tune it to your specific needs. You can easily enable and disable features, and replace core classes with your own implementations.


    Hope that helps!

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex