[Haskell-cafe] Monad of no `return` Proposal (MRP): Moving `return` out of `Monad`

[Bardur Arantsson]

On 10/08/2015 01:39 AM, Mike Meyer wrote:
> On Wed, Oct 7, 2015 at 6:05 PM Brandon Allbery <allbery.b at gmail.com> wrote:
> 
>> On Wed, Oct 7, 2015 at 4:54 PM, Bardur Arantsson <spam at scientician.net>
>> wrote:
>>
>>> Please consider that the the way practical development really happens[2]
>>
>> ...among web developers, who of course are the only real developers?
>> [...]
>> I had heard that the financial users generally refused to have anything to
>> do with the Haskell community.
>> Now I know why.
>>
> 
> I'm curious - do "practical" developers really feel like they have to rush
> out and update their tool chain whenever a new version of part of it comes
> out? Most of the projects I've worked on considered the language version as
> a fixed part of the technology stack, and almost never updated it. Even
> when using Python, which valued not breaking working code more than it's
> own zen. But changing anything that potentially affected all the code in a
> working project was pretty much never done, and always involved a lot of
> effort.
> 
> So the worst headache I got from language evolution was from trying to
> remember which set of features I had available for each project. No, that's
> second - the biggest one was from arguments about when we should adopt a
> new version. But breaking working code pretty much didn't happen.
> 

+1, that's an excellent point well made.

I have been in this situation and it was certainly frustrating *as a
developer*, but it pretty much works for most businesses.

Regards,