[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[jfw] Re: Packages - Keep or Dump?

I think this is not a proper question for this time.

The truth is that there are better packages out there and that's why developers choose them, Joomla brand is not enough.

We should start architecting new CMS generation and then see which packages out there are best for this task. If some of the Joomla Frameworks fit most, let's keep them.
And depreciate the rest.

For example: Database package is not bad, but I'd rather use Laravel's Eloquent or Doctrine DBAL, as it's much more mature and has multiple drivers support built in. Seriously - we can't compete with these.

On Monday, May 25, 2015 at 9:34:06 AM UTC+2, Robert wrote:

Am Sonntag, 24. Mai 2015 18:09:35 UTC+2 schrieb Michael Babker:
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:

- Facebook

I tried this one in a project and could get it running so drop it. 



Framework source code: https://github.com/joomla-framework
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/group/joomla-dev-framework.