@PaulieScanlon Hello! Sorry for the slow response, I don’t make it on here much. Did you figure out what you needed to re:hexasphere.js? I saw your Edge visualization if that is what you were working on at the time - looks great!
@DavidBrocek@SierraChest I agree. It worked back then. I wouldn't have such fond memories of the games if they were easy (and fair). I do wonder what percentage of Sierra's revenue came from the 1-900 tip line and hint books though ;)
@MutableBall I hate software versions. But comparable how? Every versioning scheme I've seen at least allows you to compare for equality (mostly?). Then it comes down what other information you'd like to encode into the version, and it's hard to imagine a one size fits all solution to that.
@MutableBall What kind of change to the Docker image? I’d think if it’s a change to the Dockerfile that you’ve checked into the repo it’s pretty natural to consider that an upgrade to the application, therefore new version for both. But I suspect this is something different?
@lzsthw The 1st is a bit more concise and signals a RESTful API, so without reading documentation API consumers can infer a whole lot (how to list all resources, how to update/delete resources, etc). I personally prefer to design my APIs like https://t.co/nB7GOIdfL1 though.
@natfriedman Thanks for publishing this data through an open API, it really is awe inspiring. I took a pass at visualizing the data on a globe in real time as well, with a little cinematic flare (click the 'GitHub Stream' icon): https://t.co/WWGJlhE1cp