Dominik Picheta

I disagree. Failing because a library cannot compile due to a change in API is better than failing because the versions don't match. In the latter case the packages may...

https://github.com/nim-lang/nimble/issues/127 On Thursday, 13 October 2016, Ruslan Mustakov [email protected] wrote: > By the way, Facebook announced Yarn > https://code.facebook.com/posts/1840075619545360/yarn-a-new-package-manager-for-javascript/ > - a new package manager for JS a couple of...

There is a good point made here: https://news.ycombinator.com/item?id=13378637 > 1. Software using Semantic Versioning MUST declare a public API. We need to keep this in mind. Not all Nim packages...

Yes, my point is that not all packages should be forced to use semver.

haha, awesome

> The main reason is that the R2 bucket is not accessible from our build infrastructure. Why is that? Can't we make the R2 bucket accessible from there?

Since this breaks the memory snapshot format, it's a good time to add a version header to the memory snapshots so we can more easily support multiple versions of them.

I also wonder if we could use capnp for the memory snapshot in JS

Late reply, but that is weird. Maybe some weird caching? Choosenim just requests a URL from nim-lang.org for the current `stable` version of Nim.

Yeah, sorry, right now I'm very much still prototyping a lot of gamelight. I am using some pretty specific commits of chroma, flippy etc. I'd recommend steering clear until I...