I have a simple question along this line: How does expanding the capabilities 
of Swift detract or impair its use in a fully OO manner? From what I have seen, 
if you want to use it in a strictly OO manner, great! If you want to use it in 
a strictly functional manner, no problem. If you want to use it in hybrid mode, 
go for it.

Giving developers the flexibility to code in the manner they are most 
comfortable with can only improve creativity and productivity. It also improves 
the appeal of the language to others.

Unless, of course, I am missing something here.

On Feb 9, 2017, 1:09 PM -0500, Jan Neumüller via swift-users 
<swift-users@swift.org>, wrote:
> This is just for explanation. I have given up for the content, the world does 
> move in this direction and I can’t stop it.
>
> > On 9 Feb 2017, at 18:29, Cihat Gündüz <cihatguend...@posteo.de> wrote:
> >
> > @Jan: Your arguments are very subjective if not even insulting and 
> > derogatory to many people who invest a lot of time and effort in crafting 
> > those things you despise so openly. Here are just a few example quotes for 
> > you to reflect your language:
> >
> > "I despise fp“, „is so annoying“, "made Swift imo a worse language“, "I 
> > hate ‚modern' or as I call it ugly“, "Today’s standards are a bag of pain“, 
> > "crappy sites als Facebook, Twitter, Instagram, Stackoverflow, add lots of 
> > other 'cool' sites“, "I can’t stand scrolling“, "I hate both“, "todays 
> > absolutely useless crap“, …
>
> FP: I think many coders hate it with a passion, a fact fans of fp don’t 
> generally like. For me it’s the total brain breaking “logic” behind FP and 
> lambda calculus. I started programming with assembly on mos6502 and  took 
> most languages since then. There is one family I never got my brain wrapped 
> around it as it works against the complete working of my brain: functional 
> programming.
>
> And yes I think the push for more fp elements made Swift a worse language. 
> How is that an attack?
>
> How should I call stuff that induces eye strain and headaches from usage? 
> Todays modern web technics most often lead to imo totally bad websites that 
> are a clearly worse then most sites before the web 2.0 hype. Sorry if I am to 
> direct as a german but dancing around topics is a waste of time.
>
>
> > Please be aware that this behavior is against the Code of Conduct of the 
> > Swift Community. Let’s try to stay objective and justify different opinions 
> > rationally instead of personally. Of course it is valid for you to say that 
> > you don’t like FP or that you don’t like how the world is changing in 
> > general. But please be aware that you have to add the reason why you think 
> > it is so in detail, so we understand your thinking and can overcome changes 
> > to the wrong direction. Senctences like „I despise FP“ without any 
> > explanation are not a form of constructive feedback though, nobody will 
> > learn anything from that kind of thing. Currently you’re merely expressing 
> > your anger here, no more, no less.
>
> Anger? And there is no reason after gotten steamrolled by evolution on this 
> discussion by simply NOT ASKING US (Swift-Users) and simply presented a 
> decision? Should we be happy that a part of the community sees itself 
> apparently as more important then the rest? Of course I’m angry after such 
> actions - who wouldn’t?
>
>
> > @Jens: One of the biggest reasons I’m all for Discourse is the fact that 
> > it’s open source. What this implies is: You know exactly what happens with 
> > the data you save there, and, there is no dependency on a third-party 
> > service which could change or even close over time. This is why I’m against 
> > groups.io, GitHub Issues or any other non-open source solution. What it 
> > also means is: If the open source tool we decided to go for (Discourse) 
> > doesn’t have good support for emails yet, we can implement it ourselves, 
> > improve the existing support or add a bridge to another open source tool 
> > that can deal with that.
>
> Sadly Discourse stands under a license that makes contributing a nogo for 
> many. As a BSD dev I NEVER would put any of my code under GPL. This is a 
> thing we should not forget - fitting licenses.
>
> Jan_______________________________________________
> swift-users mailing list
> swift-users@swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users

Reply via email to