Total Votes (10)

I'm a sucker for good transport apps (having built several in my time) - I like the concept, especially providing something pretty generic that can be repurposed elsewhere.

Testing here is obviously hard being on the complete other side of the world, but based on the video and what testing I could do, I'd say it looks like a great starting point - more time spent on presenting the information in the future would be useful, but the integration and real time aspect is great for the weekend.

Very useful as a tool for someone who isn't a huge node developer - being able to quickly verify the popularity of libraries. I like the fact you take into account things more than just the download count - which are important when making key decisions about what to use.

Holy Crap, this is super cool. I'm pretty sure this is the simplest take on YouTube Parties I've seen before - and the idea of using randomly generated hash tags as rooms is damn cool. It worked straight up for me, videos were added instantly and it's super easy to use.

All thats missing is a way to share / view the link to the current one once videos are playing.

Very cool take on the competition idea. I love the idea of using the raspberry pi as a hardware testbed for NodeOS. Definitely looks like a lot of fun and something fun to hack with - not 100% sure how I'd use it in the real world other than to learn more about OS userland design / structuring.

Very cool idea and a neat way of getting started with Emscripten. I think it's interesting from the perspective of providing a way to test C++ code in the browser more than anything else (e.g. rather than using to implement unsupported stuff).

Out of interest, is there a reason to use a custom element versus just using a custom type on a script tag? It seems odd to add a new tag entirely, but I may well be missing something there.

Great work for the short amount of time, I'd love to see where this goes in the future.

It's definitely a useful idea - making caching easier for developers is a problem definitely worthy of being solved. Unfortunately, the obvious issue with that is that it's actually very hard to define ahead of time all the resources to expire.

It's hard to judge as there doesn't appear to be any docs on the api to revoke stuff - which is the hardest part. Likewise, it's hard to judge the caching is actually working - but the pages did update as you'd commented. My score is primarily based on that, but It's hard to judge without more details on what it's doing how it works, sorry!

Also, you mention it only caches GET requests - Ideally, that's all it should cache anyway - as almost everything else shouldn't be cacheable full stop from a HTTP perspective (e.g. POST, PUT, etc).

Hey guys - It's impressive how much you managed to get completed on the API side. I couldn't give much for the design / innovation sections, but it seems reasonably complete - there are still bugs (e.g. edge cases like invalid feeds - I tried hacker news rss and it just disappeared) and the flash of login on refresh that lost points.