<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>Right, thanks for the clarification, I shouldn't have said only Erlang Solutions.<br></div>
<div> </div>
<div>My point about Nix wasn't about Windows support or only the fact that I don't consider it a fit, but was my understanding from the design doc and proposals that Nix certainly wasn't a fit. For instance, including Nix in Erlang/OTP sounds to me like something much less likely to be included than Elixir...<br></div>
<div> </div>
<div>There is much work already into a foundation to base an Erlang PM to be included in OTP on, hex.pm, which rebar3 will be moving to as well, meaning 2 implementations of the API will already be worked on.<br></div>
<div> </div>
<div id="sig19496053"><div class="signature">--<br></div>
<div class="signature">Tristan Sloughter<br></div>
<div class="signature">t@crashfast.com<br></div>
<div class="signature"> </div>
</div>
<div> </div>
<div> </div>
<div>On Sun, Dec 28, 2014, at 06:02 AM, Dmytro Lytovchenko wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div><div>Its not up to ESL to decide what gets chosen, OTP/E/// and IUG will decide the final options and budget according to what is discussed here. But ESL may offer a person to work on this budget and this project.<br></div>
<div> </div>
<div>From my personal point of view,<br></div>
<div>- Nix has a chance because its C++ which is potentially cross platform and compiles everywhere. Also from NIH point of view - huge work was done there and it would be silly to just throw the idea away because parts of it are not compatible - this can be fixed;<br></div>
</div>
<div>- pure C or C++ implementation from scratch has a chance because its cross platform and compiles everywhere (or it should by design);<br></div>
<div>- pure Erlang implementation although doesn't exist yet only in a form of non-working bare skeleton prototype, also has a chance<br></div>
<div>- and then Elixir implementation has slim chance because carrying Elixir compiler or compiled BEAM's in OTP source may be non-desirable.<br></div>
</div>
<div><div> </div>
<div defang_data-gmailquote="yes"><div>On Sat, Dec 27, 2014 at 4:33 PM, Tristan Sloughter <span dir="ltr"><<a defang_rel="noreferrer" href="mailto:t@crashfast.com" target="_blank">t@crashfast.com</a>></span> wrote:<br></div>
<blockquote defang_data-gmailquote="yes" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Erlang Solutions certainly won't be going the nix route.<br></div>
<div> </div>
<div>
So someone should just go try it already :P. I did and gave up and<br></div>
<div>
tossed it in the garbage.<br></div>
<div> </div>
<div>
I say this because I feel the conversation is pointless and has<br></div>
<div>
completely derailed any talk of an actual solution to real problems.<br></div>
<div> </div>
<div><span><span style="color:rgb(136, 136, 136)" class="colour">
--</span></span><br></div>
<div><span><span style="color:rgb(136, 136, 136)" class="colour">
Tristan Sloughter</span></span><br></div>
<div><span><span style="color:rgb(136, 136, 136)" class="colour"> <a defang_rel="noreferrer" href="mailto:t@crashfast.com">t@crashfast.com</a></span></span><br></div>
<div> </div>
<div><div>_______________________________________________<br></div>
<div>
erlang-questions mailing list<br></div>
<div> <a defang_rel="noreferrer" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br></div>
<div> <a defang_rel="noreferrer" href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br></div>
</div>
</blockquote></div>
<div> </div>
</div>
</blockquote><div> </div>
</body>
</html>