Re: The Future of our Frameworks

On Tuesday, June 07, 2011 12:17:08 Pau Garcia i Quiles wrote:
> I had exactly the same question because IMHO there is a confusion
> between "framework" and "library" here.
> 
> Library = set of related functions and helper methods and classes
> 
> Framework = Library + a "way" of working with it (i. e. workflow,
> tools you need to use, conventions, etc). For instance, Rails is a
> framework because it imposes a set of conventions you cannot change
> (and you webapps will not work unless you follow them)
> 
> I'd say with the modularization we are splitting into *libraries*, not
> into frameworks because we do not impose a set of rules, tools,
> workflow, etc to work with it.

It's "vague on purpose", as we refer to libraries, but also more complex 
things such as Akonadi.
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
 
_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.