[erlang-questions] your first choice?

Rad Gruchalski radek@REDACTED
Fri Feb 20 17:46:39 CET 2015

On Friday, 20 February 2015 at 17:39, e@REDACTED wrote:
> On 02/20/2015 05:27 PM, Rad Gruchalski wrote:
> > On Friday, 20 February 2015 at 17:06, e@REDACTED (mailto:e@REDACTED) wrote:
> > > frameworks massively fail at the task of abstraction -- knowing
> > > "specification" is never enough for a "framework".
> > >  
> >  
> > Knowing specification is one thing, rejecting some common solutions, sometimes worked out for years of repetitive problem solving, is another thing. I think you are possibly a bit extreme in your judgement.
> >  
> i can not recognize an objection to my statement.  
There was none. Just a hint that “a framework” (or a library) is not always claiming to be “the only solution, otherwise there be dragons”. Some of them encapsulate some knowledge, is it wise rejecting on a basis “it’s a framework"? Sometimes a framework is a great learning source, for example - how to handle a protocol correctly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150220/5c80f994/attachment.htm>

More information about the erlang-questions mailing list