SolarPHP 1.0 Released 125
HvitRavn writes "SolarPHP 1.0 stable was released by Paul M. Jones today. SolarPHP is an application framework and library, and is a serious contender alongside Zend Framework, Symphony, and similar frameworks. SolarPHP has in the recent years been the cause of heated debate in the PHP community due to provocative benchmark results posted on Paul M. Jones' blog."
blog (Score:4, Insightful)
Yet another... (Score:4, Insightful)
Yet another PHP framework. Won't this ever stop? Won't the development efforts ever be directed to only a handful of frameworks, to get the best we can instead of a gazillion half-(or un-) documented, over-(or under-) engineered frameworks?
Re:Yet another... (Score:2, Insightful)
Yes, its totally beautiful that literally every time one gets involved in a PHP project some assclown involved has already decided to use the fad of the week framework, increasing frustration and limiting productivity as you search furiously for the non-existent documentation / examples to find the "framework" way to do some mindnumbingly simple operation that should have never been wrapped in a framework in the first place.
Invariably the individual who has decided to use the framework usually has worked with it on a limited basis if ever before, and only wants to learn it because he's heard on some blog that it will increase his productivity. Since the average framework has a lifecycle of approximately 1 project all he's really done is slowed development of that project immensely to pick up a braindead API he will never see again.
Re:Yet another... (Score:3, Insightful)
I don't know if you're trying to be funny but what you describe is framework spaghetti. Everybody thinks they know how to do it better, so they keep reinventing the wheel - poorly. Producing frameworks that aren't stable aren't frameworks, it's just make as you go implementation with a nice name and likely to be thrown out and started all over again by the next guy who favors a different one because nothing is really standard or a convention. But I suppose it keeps web developers paid...
Re:Yet another... (Score:3, Insightful)
This is what is so annoying about all these new frameworks.
From a business point of view I will not develop with anything other than the most popular frameworks because if I need to hire a contractor, or even a new employee, it is more cost effective to use a popular framework that I don't have to train them in.
Re:Yet another... (Score:3, Insightful)
I agree. The last 6 projects I've had the misfortune to take over were like this... unwieldy, evilly complex and error stuffed. What should have been simple was insanely complex. It took 4 to 6 weeks just to get anyone working on anything. I could have coded it in flat PHP in 2 days. Frameworks are the death of projects and its one of the reasons I no longer love programming.
Re:Rails 3.1 Comparison (Score:3, Insightful)
You may have a valid point, but I can't get over the trollish way you souped up those code examples to prove your point. You made the PHP example over-commented, bulky and redundant on purpose. A more accurate counterpart would more likely look like this:
public function actionIndex()
{
$this->list = $this->_model->blogs->fetchAll(array(
'where' => array('blogs.status = ?' => 'public'),
'order' => 'blogs.created DESC'
));
}
Without knowing the actual library used for the PHP example, there might be saner and less ugly variants.
But it also allows new things to happen (Score:4, Insightful)
"Real" developers love to hate PHP because it goes against their rules, meanwhile the little language that could is the largest web language around. More site are run on PHP then anything else.
Why? Because it can. All the devs who want standards and a standard framework are the kinda dev's that take six months to produce the first draft of the first requirement pre-meeting agenda action point item. Sure, that is great if you work for the state or the fortune 500, but the new stuff happens with tiny companies started in someone's garage where the code has to be working yesterday.
As soon as other languages become capable of "just producing a site now", then PHP will start to becomes less dominant.
And yeah, this practice does result in thousand of badly written site in urgent need of being cleaned up. That is not a bad thing, if it was left to the ruby crowd, those sites would never have seen the light of day.
For people who understand business, having to rebuild your shop because it has become to small after a year is NOT a sign that you chose the wrong shop. It is a sign you did well. Only developers totally removed from the realities of daily life don't get this.
Oh and if you need conventions in your programming, aren't you really saying someone needs to hold your hand? For me the only quality measurement that works for software in the end is "does it allow the owner to make money". It can be the most horrible spaghetti code you ever saw, but if it allows the company to flourish and grow, then it is good code. I have seen to many "proper" development on very large projects that followed all the conventions and produced steaming piles of crap that were unusable. Look to every single government IT project for examples.