<codec_>
ah I didn't know we could put a reference capabilites in the constructor
<codec_>
this is neat
<SeanTAllen>
ya
<SeanTAllen>
very very handy
<SeanTAllen>
hope that helps
<codec_>
a lot
<SeanTAllen>
i need to run and do some stuff
<SeanTAllen>
ill be back on in a few hours
<codec_>
no problem
<codec_>
take your time
<codec_>
thanks for the tips
<SeanTAllen>
you're welcome
<SeanTAllen>
happy ponying!
dipin has quit [Quit: dipin]
<SeanTAllen>
o, before i go codec_. i'm interested in hearing what your Github/Pony stable worry was.
<codec_>
what do you mean by that?
<codec_>
ah yes I remember
<codec_>
From what I understand (I may be wrong) but pony stable use git as a dependency tool
<codec_>
But git repositories may be deleted and broke a lot of code reliying on it
<codec_>
So having a tool delivered with the pony ecosystem that connect to a server where it can fetch the appropriate dependency should be more reliable
<codec_>
Plus, it would get rid of Git as a dependency for pony stable (even if it is a dependency that can be satisfied easily)
<SeanTAllen>
You dont have to use git. It's one option.
<SeanTAllen>
You can download the code from whereever and keep it and point pony stable at the local directory.
<codec_>
sure, but ain't the purpose of Pony Stable to fetch dependency?
<SeanTAllen>
fetch is one thing it does
<SeanTAllen>
in the end, it manages your PONYPATH so dependencies can be found.
<SeanTAllen>
if dependencies disappearing from an external source is a concern, i would think one would to make their own copies.
<SeanTAllen>
or you could fork your dependency on github and fetch it from there
<SeanTAllen>
GitHub is going to be far more reliable than whatever someone throws up for hosting
<codec_>
I disagree, for example NPM does not allow to remove published package after it has been uploaded (except for the 24 first hours)
<codec_>
I thinks crates.io discourages it too
<SeanTAllen>
Pony stable doesnt require you use Git.
<SeanTAllen>
If you would like to start running something like NPM for Pony stable, feel free.
<SeanTAllen>
I don't have the money to do that.
<codec_>
don't take it personally
<SeanTAllen>
I'm not
<SeanTAllen>
I do think you are confusing a policy with a mechanism.
<SeanTAllen>
NPM could disappear tomorrow and everything would be gone.
<SeanTAllen>
GitHub could disappear tomorrow and everything could be gone.
<codec_>
sure, but in practice it won't
<codec_>
and generally the package on npm have their source on github
<codec_>
which give 2 level of safety
<SeanTAllen>
Well in practice if I want to use Git, I can make fork of the project and be sure it wont go away.
<SeanTAllen>
That's policy, not mechanism.
<SeanTAllen>
Git is purely a mechanism.
<codec_>
sure but the burden of forking and updating every repository is quite high
<codec_>
you are right in the sense that git is only a mechanism, but if you want to add an extra safety at the community level how you would do it?
<SeanTAllen>
honestly i have other things that i think are more pressing to address for Pony.
<SeanTAllen>
if someone wants to start an NPM/crates.io for Pony that would be awesome.
<codec_>
the problem is that it shouldn't be a single person because then the problem is the same. It should be an organization manged by multiple persons. That way it gives stronger guarantees.
<codec_>
But I agree with you it shouldn't be a priority for now,as there are probably a ton of things to do before needing that
Praetonus has joined #ponylang
vaninwagen_ has joined #ponylang
dipin has joined #ponylang
dipin has quit [Client Quit]
dipin has joined #ponylang
sima has joined #ponylang
sima has left #ponylang [#ponylang]
vaninwagen_ has quit [Ping timeout: 240 seconds]
vaninwagen_ has joined #ponylang
<vaninwagen_>
codec_, i've just reviewed your tutorial contributions, great stuff! thank you very much!