On 26/07/16 14:55, Neeraj Sharma wrote:
Cannot argue with that considering the use cases for the choice of rumprun definitely puts additional constraints on application design and deployment and probably rightfully so.
Yup. If you try to put a modern BMW engine in the Ford Model T, you're going to have a bad time. Working out which is which in the analogy is left as an exercise to the reader ;)
I believe you are correct but it does complicate the changes required in the Erlang package which as it appears favors Linux for its internal architecture. Having said that I do believe given sufficient publicity (to gain support within the Erlang maint community) and enhanced understanding should take care of some of that if not everything.
Even before taking things to the Erlang community, there should be a strong understanding of the scenario and tradeoffs. I'd simply not worry about the Erlang community for now, at least unless you have exceptionally friendly/casual relationships with them.
Again, we can't compete with Linux at their game, simply don't have the headcount. (then again, one might argue that writing a Unix clone in the 90's was pointless, but here we are)
