Nooku Framework, why should you care ?

Us developers are inherently lazy. Yes it true ! New technologies we greet with the needed scepticism. After all, why should we adopt a new technology if our existing tools work fine ?

The public release of Nooku Framework, now almost a year ago, was no different. Some people were very excited while others welcomed the framework with some reservations.

A few days ago Torkil Johnsen, Nooku Community Contributor, wrote an excellent blog post titled : “What is this Nooku Framework thing really ? And why should I care ?”

In his post Torkil does a great job explaining what Nooku Framework is all about, how it differs from the Joomla Framework and why he thinks you should care.

What is a framework ?

Torkil starts with defining the term framework and the benefits of using a framework in general :

Saves time. By eliminating the need to code repetitive tasks. You can focus on what’s important: Finishing the application and making sure it meets the requirements.
Less bugs. The parts handled by the framework have been used and tested earlier. The more framework code you use, the less bugs you will experience.

Which frameworks for Joomla exist ?

He then moves on to explain the difference between extension frameworks, like Nooku and template frameworks, like Gantry.

“Nooku and Joomla try to accomplish the same thing: To make developing Joomla components, plugins and modules easier. This is primarily stuff happening under the hood you might say. Gantry however is a framework made by Rockettheme to make developing Joomla templates easier.”

In recent months many different template frameworks have emerged, Morph, Wrap5, Motif, Rumi, JA T3, … to name a few.

To date however, Nooku Framework is the only community driven open source framework for Joomla extension development. Something we are very proud of !

Why choosing for Nooku Framework ?

Finally Torkil explains why he prefers Nooku Framework over the Joomla Framework.

  • It’s reduces code. It reduces the amount of code I need to write by something close to 80%.
  • It makes me better. Nooku reuses solutions to common problems (design patterns) to a greater extent, and unlike Joomla it forces me to adhere to conventions and standards.
  • It’s Joomla compatible. Any Joomla website that needs custom functionality can start using Nooku to build that functionality, today. It installs like any other extension, and does not interfere with Joomla or your installed extensions.
  • It’s the second generation. Yes, literally the second generation. Both the Joomla and Nooku Frameworks were built by Johan Janssens. Today, Johan is still considered to be the largest contributor to the Joomla codebase
  • It’s got a developer community. Unlike Joomla, development at the framework level is moving forward at a rapid pace, there is lots of activity, and developers are sharing and contributing code between themselves.
  • It’s cheaper. I know; too obvious. Less time spent programming + Less bugs = Lower development and maintenance costs.

Torkil’s concludes : “If you’re a programmer yourself, go check it out at http://www.nooku.org/framework.html. If not, you should talk to whoever does the programming for you and make sure that they do.

I couldn’t agree more !

  • http://imagik.org/programming/?p=13361 Nooku Framework, why should you care ? « Nooku Blog | Programming Blog Imagik.org

    [...] is the original post: Nooku Framework, why should you care ? « Nooku Blog No [...]

  • http://neorack.com/?p=13847 Nooku Framework, why should you care ? « Nooku Blog | Neorack Tutorials

    [...] more here: Nooku Framework, why should you care ? « Nooku Blog Share and [...]

  • http://topsy.com/blog.nooku.org/2010/07/nooku-framework-why-should-you-care/?utm_source=pingback&utm_campaign=L2 Tweets that mention Nooku Framework, why should you care ? « Nooku Blog — Topsy.com

    [...] This post was mentioned on Twitter by nooku, Flavio Copes. Flavio Copes said: RT @nooku: Nooku Framework, why should you care ? http://bit.ly/c5fBjc [...]

blog comments powered by Disqus