Trine – A utility library for functional programming in JavaScript

Post by colin_jack » Fri, Jun 12, 2015, 6:58 AM UTC

delluminatus wrote: post #73

colin_jack wrote: post #53

Earlier quoted context omitted.

You have a point but you mention C#, it's worth thinking of how you'd handle one of the examples in C#: items .filter(isOk) .map(toOtherType) ::flatten() In C# that sort of case is primarily handled by extension methods. They have their issues not least in terms of collisions, but to me they are a beautiful solution. The equivalent in JS would seem to be the always unpopular choice of adding these methods to the prot…

I think extension methods in C# are basically a way to work around the fact that you can't just stick a method on the prototype like you can in Javascript. I also like the C# solution, actually, I just love C#. It's a great "daily driver" language in my book. If you took the function bind syntax to its natural extreme, you end up with a model like Python or Nim, where all instance methods accept their "this" as a fir…

Post by eueueu » Fri, Jun 12, 2015, 11:53 AM UTC

escherize wrote: post #75

eueueu wrote: post #39

Earlier quoted context omitted.

This isn't the core language changing though. This is people who are new to javascript coming to it and deciding they all must write their "hello world" framework / extension. Most of it is just superfluous fluff that doesn't actually do anything but change the syntax to something they perceive as fundamentally better, when it's just a matter of taste and fashion.

I'm not sure it's purely a matter of taste and fashion. Let's say I make a new language called javascript++. Instead of having `function` be a keyword, I chose `functioooooooooooooooooooooooooooon`. Based on their syntaxes, do you find one fundamentally better?

Post by quinnirill » Fri, Jun 12, 2015, 5:28 PM UTC

CrossEye wrote: post #114

quinnirill wrote: post #109

Earlier quoted context omitted.

With Trine this would be function process () { return this ::filter(isOk) ::map(toOtherType) ::flatten(); } and then later: groupsOfItems::map(process); Granted, the `flatten` function is not in the Trine yet, somehow forgot that from the initial release.

Ok, that helps make it a bit more palatable to me. Thanks for the information. One question, though: How do user functions interact in here? If you didn't include `flatten`, but I had my own version of it, would it be straightforward for me to build `process` using my own `flatten`? Do I have to modify some Trine objects, or can I use some simple function references? Obviously I haven't yet actually dug into the Trin…

    function * flatten () {
      for ( const item of this ) {
        yield * item;
      }
    }