Question Complaints about Mootools

I am a little confused, I can't see work in progress anywhere in your post.

Goreman gave you a definitive answer now.

Time for me to leave the conversation.

*** Topic moved and subject changed ***

When this topic started 7½ months ago, it was the opinions of some users that the Kunena project should be aware about how "expensive" it was to have to use Mootools. Everyone is entitled to an opinion but I think we think carefully how we express those opinions.

Mootools is an integral part of Joomla and is a fundamental requirement of Kunena but this topic has long strayed from the purpose of the General Talk about Kunena category which is where people can comment or offer suggestions the Kunena product, this website and plans for the future. This topic has consistently been an unending stream of complainst about Mootools.

The basis of arguments against Mootools: These arguments are based on assumptions derived from the use of unnamed analysis tools; these tools look at the ingredients of a user's webpage and calculate the relative density of each of those parts. These analyses are calculated on a one-time, "snapshot" basis; the conclusions are are not intended to be scientific proof that a person's site is in urgent need of an overhaul. These tools are indicators of possible areas for improvement. Some of these tools conclude that Mootools represents a significant proportion of a site's download "cost" to the end user. This may be true - we are not denying the evidence - but, notwithstanding this truth, the fact remains that if people want to use Kunena they need Joomla with its Mootools library.

Many people put their complete faith the advice of these [unnamed] analysis tools instead of listening to their users. It would be curious to run same web analysis tools on this site and we may discover other fascinating information. Does knowing that information change the way that this site runs or how it might better run according to the conclusions of such analysis tools?

The facts: Kunena needs Joomla to run. Joomla needs Javascript to work, Kunena needs Javascript to work and without Mootools neither Joomla nor Kunena will work. These are the facts. If web analysis tools suggest that the size of the Mootools library is a factor that adversely contributes to a website's overall improvement then that, too, is a fact.

The real question is how to carry forward this topic. I have moved the topic and renamed the subject to our Miscellaneous, off-topic and general Joomla category but, for me, it is probably time that I left this conversation, too.