[Haskell-cafe] rolling span and groupBy for lists

Mon Feb 5 20:50:51 UTC 2018

If there are genuine priorities and if we can afford the luxury to have
those priorities, yes I agree with you. But Haskell is a tiny community
with little resources. Our chances of survival and winning are much
brighter if all of us put our efforts in one direction rather than dividing
them up into tinier parts, in other words set your priorities right for
success. There is no "greater good", everything boils down to our own good,
if the ship sinks we all sink together with it. Most successful projects
are successful because of the focused efforts driven from top. Diversity
and competition is always good as long as it is driven by genuine needs. I
sincerely wish that SLURP is successful and mitigates all problems plaguing
the ecosystem, but I doubt that the wish will come true.

-harendra

On 6 February 2018 at 01:57, Matt <parsonsmatt at gmail.com> wrote:

> I disagree that this is a disaster waiting to happen. Other language
> communities have multiple competing ideas and implementations, and it
> doesn't harm them too much. Haskell is still rapidly evolving and serves
> many different distinct sub-communities and needs, and it would be very
> surprising indeed if a single solution worked for all of them.
>
> Forcing (or even requesting) people to abandon their priorities and goals
> for "the greater good" will not work. Infrastructure that allows for code
> reuse and cooperation across distinct priorities will allow these
> sub-communities to grow and prosper. It's best if each community solves
> it's needs as well as it can, and allow the good ideas to spread via
> cross-pollination.
>
> Any new initiative that seeks to unify disparate groups without
> acknowledging their differing priorities and goals will fail. I don't know
> what will work, but friction is rarely resolved by increasing pressure.
>
> Matt Parsons
>
> On Mon, Feb 5, 2018 at 12:34 PM, Brandon Allbery <allbery.b at gmail.com>
> wrote:
>
>> We have two groups of "leaders", with partially opposing goals. This is a
>> disaster looking for an excuse to happen.
>>
>> On Mon, Feb 5, 2018 at 2:29 PM, Harendra Kumar <harendra.kumar at gmail.com>
>> wrote:
>>
>>> On 6 February 2018 at 00:33, Sergiu Ivanov <sivanov at colimite.fr> wrote:
>>>
>>>> Thus quoth  Harendra Kumar  on Mon Feb 05 2018 at 18:30 (+0100):
>>>> > Yes, Hayoo seems to be giving better results, I found more variants
>>>> having
>>>> > the behavior I want, it seems this variant is quite popular but still
>>>> not
>>>> > in any standard libraries.
>>>> >
>>>> > Interestingly the problem of too many choices and no standard one
>>>> that can
>>>> > be discovered applies to search engines as well. In this case there
>>>> are
>>>> > only two choices but still it is of the same nature. I knew about
>>>> hayoo but
>>>> > forgot to use it in this case. How much time should one spend on
>>>> finding a
>>>> > trivial function before giving up and making the choice to write
>>>> their own?
>>>> > I wish there was a standard, quick, good quality way of discovering
>>>> what to
>>>> > use.  It seems the Haskell ecosystem DNA encourages more and more
>>>> > fragmentation rather than consolidation. I think the community/leaders
>>>> > should acknowledge this problem and work on making things better in
>>>> the
>>>> > short/long run.
>>>>
>>>> A Single Liberal Unified Registry of Haskell Packages (SLUPR), an effort
>>>> in this direction, has been recently announced:
>>>>
>>>
>>> Unfortunately, in my opinion, SLURP is taking things exactly in the
>>> opposite direction. I was talking about the problem of choice above and
>>> SLURP is giving even more choices  and therefore encouraging more
>>> fragmentation. We should have just one good choice to stop wasting time and
>>> energy finding the best choice among millions available. Everyone should
>>> focus on making that one choice better rather spending energy in creating
>>> their own alternatives. This is where the Haskell ecosystem philosophy
>>> differs, it provides many choices in all aspects, it may be good in some
>>> cases but not always. SLURP is a technology solution which exactly fits in
>>> the same DNA. Technology can help us achieve the tasks that we set out to
>>> do but technology cannot motivate and influence us in what we choose to do
>>> and therefore ti cannot make the community focus on one goal - that
>>> requires real people leadership. If we do not focus on one goal, even with
>>> the best technology we may not succeed. Just my 2 cents.
>>>
>>> -harendra
>>>
>>>
>>>
>>>>
>>>>
>>>> > -harendra
>>>> >
>>>> > On 5 February 2018 at 22:02, Sergiu Ivanov <sivanov at colimite.fr>
>>>> wrote:
>>>> >
>>>> >> Hello Harendra,
>>>> >>
>>>> >> Thus quoth  Harendra Kumar  on Mon Feb 05 2018 at 16:43 (+0100):
>>>> >> >
>>>> >> > The irony is that theoretically you can find a Haskell package or
>>>> >> > implementation of whatever you can imagine but quite often it
>>>> takes more
>>>> >> > time to discover it than writing your own.
>>>> >>
>>>> >> Sometimes Hayoo! helps me out in such situations:
>>>> >>
>>>> >>   http://hayoo.fh-wedel.de/?query=groupBy
>>>> >>
>>>> >> utility-ht shows up.
>>>> >>
>>>> >> --
>>>> >> Sergiu
>>>> >>
>>>>
>>>>
>>>> --
>>>> Sergiu
>>>>
>>>
>>>
>>> _______________________________________________
>>> Haskell-Cafe mailing list
>>> To (un)subscribe, modify options or view archives go to:
>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
>>> Only members subscribed via the mailman list are allowed to post.
>>>
>>
>>
>>
>> --
>> brandon s allbery kf8nh                               sine nomine
>> associates
>> allbery.b at gmail.com
>> ballbery at sinenomine.net
>> unix, openafs, kerberos, infrastructure, xmonad
>> http://sinenomine.net
>>
>> _______________________________________________
>> ghc-devs mailing list
>> ghc-devs at haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20180206/c3d4e7e9/attachment.html>