MapleScala

Page 4 of 4 FirstFirst 1234
Results 46 to 51 of 51
  1. #46
    BloopBloop Hilia is offline
    MemberRank
    Aug 2012 Join Date
    905Posts

    Re: MapleScala

    Quote Originally Posted by retep998 View Post
    You were expressing uncertainty regarding the performance of fancy iterator stuff, like filter and foreach, compared to handwritten loops. Since that difference alone is not an algorithmic difference, and I know from personal experience that iterators can be implemented very efficiently (see Rust), I therefore classified it under premature optimization. Now if you did benchmark the various techniques and get some numbers to demonstrate that iterators are significantly slower than the equivalent handwritten loop, then that optimization would no longer be premature.
    I have actually tested this in C# some time ago ( i can't talk about scala) where i looped though almost all types in the assembly at start up and in that case LINQ was slower, by 25% now uh.. 25% is that much? , uhm not really since i am talking about mili seconds( i don't have the code any more or the exact time but the impact was so low that i desided to go for LINQ since i found it more readable) and so i agree that it is premature optimizing (atleast in the case of C#)

  2. #47
    Proficient Member ALotOfPosts is offline
    MemberRank
    Sep 2014 Join Date
    181Posts

    Re: MapleScala

    Quote Originally Posted by retep998 View Post
    You were expressing uncertainty regarding the performance of fancy iterator stuff, like filter and foreach, compared to handwritten loops. Since that difference alone is not an algorithmic difference, and I know from personal experience that iterators can be implemented very efficiently (see Rust), I therefore classified it under premature optimization. Now if you did benchmark the various techniques and get some numbers to demonstrate that iterators are significantly slower than the equivalent handwritten loop, then that optimization would no longer be premature.
    You quoted the wrong person? Nothing in his post is about filter and foreach

  3. #48
    PeterRabbit retep998 is offline
    MemberRank
    Apr 2008 Join Date
    VanaLocation
    707Posts

    Re: MapleScala

    Quote Originally Posted by ALotOfPosts View Post
    You quoted the wrong person? Nothing in his post is about filter and foreach
    Erk, you're right. Fixed my post.

  4. #49
    Account Upgraded | Title Enabled! oxysoft is offline
    MemberRank
    Nov 2008 Join Date
    Canada, QCLocation
    1,400Posts

    Re: MapleScala

    ITT: op who doesn't know anything about scala starts writing a game server meanwhile other ppl argue over stuff no one cares abt

  5. #50
    Account Upgraded | Title Enabled! aaronweiss is offline
    MemberRank
    Apr 2012 Join Date
    351Posts

    Re: MapleScala

    Quote Originally Posted by Snakeday View Post
    aaronweiss: Yes there were some constructive points but overall your comments were rather toxic. For example you have yet failed to mention that not all scala users/advocates actually favor a highly functional style, Scala is a multi-paradigm programming language. Feel free to treat it as such.
    It's a multi-paradigm language because it more-or-less has to be to have Java interop. There are few Scala programmers who don't use functional idioms, and for the most part, those people are basically just writing Java. There's little point to using a different language if you're not going to take advantage of the features it gives you.

  6. #51
    Account Upgraded | Title Enabled! oxysoft is offline
    MemberRank
    Nov 2008 Join Date
    Canada, QCLocation
    1,400Posts

    Re: MapleScala

    Quote Originally Posted by Snakeday View Post
    Scala is a multi-paradigm programming language. Feel free to treat it as such.
    this is the dumbest thing I've read all week, good job

    Quote Originally Posted by Snakeday View Post
    retep998: You are making the common mistake of misclassifieing something as premature optimization. If I have a given problem and can choose between two algorithms of which I know that one is faster and both are equally readable I should always choose the faster one
    except when the difference is fucking insignificant and/or it hinders readability significantly

    Quote Originally Posted by Snakeday View Post
    [...] comments were rather toxic [...]
    [...] by the toxicity [...]
    it's like you came straight from tumblr, you fucking waste of oxygen



Page 4 of 4 FirstFirst 1234

Advertisement