[Kss-devel] Why not to use KSS?

[Godefroid Chapelle]

Hi Jeroen,

Thanks for taking the time to chat with Martijn !

I was wondering what were his thoughts : I am very happy to be able to 
go through them.

I'll be giving my thoughts about this mail on this list asap. But I'll 
take time to make a wise answer (sic) rather than an emotional one...

Jeroen Vloothuis wrote:
> During a chat session with Martijn we came to the following list of 
> problems with the current state of KSS. Note that these are my 
> interpertations of his objections. Anything might be misrepresented by 
> me (so don't blame him ;-).
> 
> Problem descriptions:
> 
> Problem number one is the filesize. KSS is easily on of the biggest JS 
> frameworks out there. Compared to libraries such as JQuery etc. it is 
> massive. To make matters even worse you actually need extra libraries if 
> you want effects or anything similar.
> 
> The second problem is that KSS adds an extra runtime to the browser. 
> This directly relates to problem one in that it makes the client load 
> greater.
> 
> A third problem is that KSS is more of a framework than a library. This 
> means you have to drink the cool-aid in order to use it.
> 
> And the framework point brings us nicely to the final point in that KSS 
> is not flexible enough. Martijn gave some examples of applications in 
> which he wanted more done on the client (on example was filtering a list 
> of options based on some selects etc.). This could be done with KSS but 
> the overhead of writing plugins etc. did not outweigh any advantages 
> (especially not since he wanted less bloated server communication as well).
> 

<snip>
-- 
Godefroid Chapelle (aka __gotcha)- BubbleNet  http://bubblenet.be