Michael Van Sickle

I'm trying to figure out if you're asking for help, venting, or signaling the start of "gocode 2.0". If you're looking to drum up some interest, you might want to...

I've been thinking about taking this issue over the past couple of days. The way I see it, there are several paths that one might want to take when they...

One approach that could be used is to create a hash for each demo project and store it every time a demo is processed. A task could then be added...

If the processing and hash updates are done as part of a contributor-driven task, it could be preceded by the task that zips up each demo to simplify the creation...

Using the .zip files won't work since the file changes each time, presumably due to metadata that is stored in the zip file (time of archiving, etc.). Instead, I am...

There is a reference to this article in the fifth tutorial

@devpaul this is exactly what we need with this article. The only thing I would caution is to not go too deeply into the testing topic. We will have a...

While I don't have a strong opinion on several of these points, I do think that wrapping WebSockets in a dojo/request-like interface makes a lot of sense. While WebSockets can...

Observables make sense from the perspective of the server sending data down to the client, but there would also have to be an aspect of the API to cover the...