若J1.6真如官方所言的达成其中大部分目标，同时在性能上有所提升，则用户和开发者或会重拾对其的信心。

或者说，从1.6开始，核心功能即开始有向理想中的快速建站CMS靠近的趋势。

见：Feature patches for 1.6

  • Implement a new JForm library package [complete].
  • Implement a simple way of providing translation in JavaScript [complete].
  • Implement new controller dispatchers for more robust request routing [complete].
  • Implement a new access control system that needs to at least emulate what is in 1.5, allow adding of new groups and access levels, and allow you to set new "view" rules for at least articles [nearly complete].
  • Implement and standardise several new event triggers [in progress].
  • Implement a JContent class that will be used by content plug-ins and views [in progress].
  • Upgrade to Mootools 1.2 [in progress].
  • Finish the new extension updater work [in progress].
  • Menu manager re-work -- added since it's broken in 1.6 [in progress].
    另外，1.6最终版本预期包括
  • Implement unlimited depth categories (but not multi-mapping).
  • Refactor the user management system and make it more extensible (eg, allow custom user fields).
  • Implement a comments system (including pings and track-backs).
  • Implement queued redirects (allows you to, for example, return to the previous page you were on after you edit something).
  • Refactor parameters and make them more extensible (for example, plugins could allow you to add additional custom parameters to articles).
  • Finish MVC-ing the Administrator components (we need lots of help here).
  • Implement CAPTCHA helpers for any form.
  • Implement systems whereby external authentication systems, such as LDAP, can map to our new Joomla user groups.
  • Re-implement the ability to select multiple categories for some views in com_content (was in 1.0, got dropped in 1.5).
  • Implement a database driven installation log.
  • Refactor JError.
  • Examine the PDF generation system in detail and see if we can make it work properly (otherwise we will look at dropping it if we can't make it work well).
  • Localise the Invalid Token messages.
  • Drop the Polls component because the quality of that extension is pretty bad and there are much better third-part alternatives available.
  • Convert all layouts to semantic, XHTML Strict.
  • Convert of ini-based "params" fields to use JSON instead of INI format (huge technical and performance improvements).  Note, the language files will remain in INI format.

当然，kolidon和同事们的理解是，对开发者来说，它的编程约定其实来得比drupal要少，虽然架构仍然过于笨重了一些。

我们试着将1.0更改成一套框架，使某些界面有较多需要的组件变为准MVC架构——比如内容组件，现在components中仅有常用方法而没有前端呈现部分，将前端部分交由smarty控制的模板，而模板按频道-栏目-栏目可单独分派。这个实验现在看来取得了初步成功，现在使用的仅仅是J1.0丰富的函数库和后端了。当然，若安装了一些新的组件，亦可不经分离的前端而直接使用。

kolidon将致力于J1.6性能提升的研究。