In article <[EMAIL PROTECTED]>,
Kay Schluehr <[EMAIL PROTECTED]> wrote:
.
.
.
>What are frameworks really good for - a very true success story.
>
>A colleague of mine used to spread all kinds of flags ( state- and
>property mar
Peter Decker <[EMAIL PROTECTED]> writes:
> On 8/16/05, Mike Meyer <[EMAIL PROTECTED]> wrote:
>
>> Well, they may have created a library class that does the job for
>> them. Figuring out which is which seemed to be the point of this
>> thread.
>
> I guess my summary of the thread was that a library
Simon Brunning schrieb:
> On 8/15/05, Rocco Moretti <[EMAIL PROTECTED]> wrote:
>
>>Which lead me to the question - what's the difference between a library
>>and a framework?
>
>
> If you call its code, it's a library. If it calls yours, it's a framework.
IOW Apache with modpython is a framework
Simon Brunning wrote:
> On 8/15/05, Rocco Moretti <[EMAIL PROTECTED]> wrote:
> > Which lead me to the question - what's the difference between a library
> > and a framework?
>
> If you call its code, it's a library. If it calls yours, it's a framework.
Pretty!
I don't think it is an oversimplific
On 8/16/05, Mike Meyer <[EMAIL PROTECTED]> wrote:
> Well, they may have created a library class that does the job for
> them. Figuring out which is which seemed to be the point of this
> thread.
I guess my summary of the thread was that a library is built to do one
thing, while a framework is bui
Peter Decker <[EMAIL PROTECTED]> writes:
> I've written several apps that need to update a database, and each one
> had to do the same things: connect, grab data, create controls to
> display/edit that data, validate any changes and then stuff the edited
> data back into the database. I started pl
Terry Hancock wrote:
> Zope recently started going through some massive changes to make
> it more like a toolkit (which is the term I use instead of library here).
> Even if there must be a framework, a thin framework with good tools
> tends to be better than a complex framework, even if they can,
Rocco Moretti wrote:
> Cameron Laird wrote:
>
>> Andy Smith rails against "frameworks":
>>
>> http://an9.org/devdev/why_frameworks_suck?sxip-homesite=&checked=1
>
>
> Slapdash Summary: Libraries good, frameworks bad - they are a
> straightjackets and limit sharing.
>
> Which
On 8/16/05, Terry Hancock <[EMAIL PROTECTED]> wrote:
> Where a framework shines is when you don't really want to program
> it much at all -- you just need a tweak here and there beyond what
> it already does. Gimp plugins are a great example of that.
I'd put it slightly differently. Where a fram
On Tuesday 16 August 2005 08:46 am, Rocco Moretti wrote:
> But I'm not sure if library vs. framework a fair comparison - the two
> are doing different things. With a framework, you're not really writing
> your own program, you're customizing someone else's. Sort
in mind, it's easy to see why Andy
Smith feels frameworks are restricting - after all, it's the framework,
not the user, who is "in charge" of program structure.
But I'm not sure if library vs. framework a fair comparison - the two
are doing different things. With a
On 8/15/05, Terry Hancock <[EMAIL PROTECTED]> wrote:
> On Monday 15 August 2005 09:54 am, Simon Brunning wrote:
> > If you call its code, it's a library. If it calls yours, it's a framework.
>
> Such concision deserves applause. ;-)
Thank you. ;-)
As others have pointed out, this is a *drastic*
Simon Brunning wrote:
> On 8/15/05, Rocco Moretti <[EMAIL PROTECTED]> wrote:
>
>>Which lead me to the question - what's the difference between a library
>>and a framework?
>
> If you call its code, it's a library. If it calls yours, it's a framework.
Trying to add my 2 cents (As I do not agree
On Monday 15 August 2005 09:54 am, Simon Brunning wrote:
> On 8/15/05, Rocco Moretti <[EMAIL PROTECTED]> wrote:
> > Which lead me to the question - what's the difference between a library
> > and a framework?
>
> If you call its code, it's a library. If it calls yours, it's a framework.
Such conc
Simon Brunning wrote:
> On 8/15/05, Rocco Moretti <[EMAIL PROTECTED]> wrote:
>
>>Which lead me to the question - what's the difference between a library
>>and a framework?
>
>
> If you call its code, it's a library. If it calls yours, it's a framework.
Erh, it's not quite that simple. I don't k
Simon Brunning wrote:
> On 8/15/05, Rocco Moretti <[EMAIL PROTECTED]> wrote:
>
>>Which lead me to the question - what's the difference between a library
>>and a framework?
>
>
> If you call its code, it's a library. If it calls yours, it's a framework.
Although that definition probably makes se
On 8/15/05, Rocco Moretti <[EMAIL PROTECTED]> wrote:
> Which lead me to the question - what's the difference between a library
> and a framework?
If you call its code, it's a library. If it calls yours, it's a framework.
--
Cheers,
Simon B,
[EMAIL PROTECTED],
http://www.brunningonline.net/simon/
Cameron Laird wrote:
> Andy Smith rails against "frameworks":
> http://an9.org/devdev/why_frameworks_suck?sxip-homesite=&checked=1
>
Slapdash Summary: Libraries good, frameworks bad - they are a
straightjackets and limit sharing.
Which lead me to the question - what's the dif
18 matches
Mail list logo
