"Frankly, we have a fair bit of code that falls into the unused or unmaintained categories that can just be deprecated gracefully, or code that may be well intended but just doesn't fit into the scope of what we do."
No, Joomla doesn't have the resources to compete with a corporate funded framework stack. But the mentality that we just give up and go play in our little corner doesn't set well with me either. No, the packages don't get a lot of traffic. And no, using the combined Framework repo which was ripped apart in Feb 2014 isn't a fair metric either, a deliberate decision (that I don't necessarily agree with) was made to stop shipping a combined framework together and go to a modular release system.That same argument about giving up IMO could be made about Joomla as a whole, just shut down development and use a CMS that's much better supported or structured.On Sun, May 24, 2015 at 3:30 PM, Johan Janssens <jjan... AT gmail.com> wrote:Hi Michael,--Instead of slimming down, I think time has come to throw in the towel. The framework/platform was created with the idea that developers could create standalone Joomla applications. Lets be honest, this didn't happen. To date, we haven't seen any major uptake in the Joomla community, nor the wider PHP community. Developers looking for web application frameworks, are choosing for Laravel, Symfony, ... or others.A little look at packagist shows that the Joomla Framework was only installed 5000+ times, compared to the more then 5 milion installs for Laravel, or more then 6 milion installs for Symfony.- Symfony : https://packagist.org/search/?
q=symfony- Laravel : https://packagist.org/ search/?q=laravelContributions to the framework have also stalled completely. There hasn't been any serious commit activity since the latest 1.1.0 release in Feb 2014. See : https://github.com/joomla/ joomla-framework/graphs/ contributorsAs for the separate packages released at https://github.com/joomla- framework, those are not getting installed a lot either, see https://packagist.org/search/? q=joomlaVery likely because there are a lot better PHP libraries available today.Think it's more then fair to conclude that the framework/platform effort has failed. Nothing wrong with that. I know it's not easy to let go, but lets not waist time and energy on something that developers are not looking for. Instead lets bundle efforts and focus in moving Joomla forward as a content management system.Johan
On Sunday, May 24, 2015 at 6:09:35 PM UTC+2, Michael Babker wrote:So the Framework has packed on a good bit of weight and carries 43 packages today. I think we need to look at putting the Framework on a diet. Frankly, we have a fair bit of code that falls into the unused or unmaintained categories that can just be deprecated gracefully, or code that may be well intended but just doesn't fit into the scope of what we do.Packages that should go:- MediaWiki- OpenStreetMapPackages that are questionable:- Archive- Data- Image- LDAPThoughts?
Framework source code: https://github.com/joomla-
Visit http://developer.joomla.org for more information about developing with Joomla!
You received this message because you are subscribed to the Google Groups "Joomla! Framework Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-framework+
unsubscribe AT googlegroups.com.
Visit this group at http://groups.google.com/