You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hey @whyrusleeping we should open this up, i wanna start using it and playing with it. feel free to open it up under protocol/ or under whyrusleeping/ or whatever you want.
once you open it up, i'll start using it + compiling feedback and post it in the repo. I'll have it as criteria:
MUST handle go-specific packaging/distribution concerns well
SHOULD handle go-specific module system concerns well[0]
MAY handle packaging/distribution concerns well
MAY handle module system concerns well
[0] go get's failure as a module system stems from not realizing a "module system" is different from a "package distribution tool". And this distinction is where npm shines (node packaged modules).
The text was updated successfully, but these errors were encountered:
You should add install directions, as well as make sure it actually works. I'll give it a try again. Might just have to try a shell script unless someone knows some make magic.
hey @whyrusleeping we should open this up, i wanna start using it and playing with it. feel free to open it up under protocol/ or under whyrusleeping/ or whatever you want.
once you open it up, i'll start using it + compiling feedback and post it in the repo. I'll have it as criteria:
[0]
go get
's failure as a module system stems from not realizing a "module system" is different from a "package distribution tool". And this distinction is where npm shines (node packaged modules).The text was updated successfully, but these errors were encountered: