On Friday, 27 January 2017 20:22:23 UTC+7, Bob Zhang wrote: > > Hi Gordon, your facts can be changed every post. > And you spent a month in tweaking your elm expert's code to match the perf > of newbie's BuckleScript code, I am still not sure you reach there. > I suggested we take the discussions off the list very very early, > most people have very busy professional life, this is gonna be my last > post in this thread.
I did not spend "a month on elm expert's code"; I spent a month off and on evaluating many JS transpilers including Elm, PureScript, GHCJS, TypeScript, Nim, Kotlin, Fable, and finally BuckleScript. I wrote the benchmarks for each in standard functional programming style including these ones for Elm and the ones for BuckleScript. The objectives of the thread are clear enough: try to make Elm faster where it isn't, and find ways to augment it when necessary. I looked into all the other transpilers including BuckleScript with this in mind. I agreed with you that an alternate way of communicating about BuckleScript would be better, and asked you to provide a means, as I didn't want to clutter your repo with issues. You did not do this. Finally, I found a significant slowdown of BuckleScript in one particular situation of running any benchmark on FireFox, and (although I didn't have to to this) traced the reason for this and the only workaround I could find, which has nothing to do with the code I wrote. In response, rather than looking into the reasons for that slowdown, you have been snarky with me, maintaining that it is the differences in the code that cause the issue rather than looking at the real issues or opening a channel so you could obtain my code to look at it for problems. You know, one of the reasons that one would choose to develop in one of these "one-man-show" languages is how the BDFL reacts to issues: in that you fail. 'bye. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
