spencerhakim

Steam has a hidden debug console that allows users to rollback any game to any previous release via the `download_depot` command. It's not remotely as user friendly as when a publisher adds an old version of a game as a beta branch that can be easily switched to in the UI, but as far as I know there's no way to prevent its use.

The Kinect is great at full-body tracking for VR, Microsoft was just a decade too early in their attempt to bring the technology to market.

> Another method that we will leverage is pay-per-use public cloud instances. With this, anyone can spin up RHEL images in the cloud and thus obtain the source code for all packages and errata

How does this approach not require them to agree to the ToS/EULA mentioned earlier in the post?

Reddit should have stuck to the Craigslist model of simply just existing as-is, selling a reasonable amount of ads and premium subscriptions, and only having the minimum number of employees required to keep the site up. It never needed to be and shouldn't have been anything more than that.

Of course, but I'm sure being a name brand helps them negotiate a larger discount.

I would be shocked if Etsy/Spotify/whoever else wasn't cutting a deal for a significant discount, getting these name brands on GCP is great PR for the platform.

Given the alternative of handing out my SSN and hoping for the best, I'd be more than happy to use this for banking and related services. Presumably, third-party use would be covered by some form of ToS, and maybe we'd see actual repercussions for leaking data that originated here.

But why June 21, 2006, specifically? According to Wikipedia, there was a circulated Pre-RC1 Vista build (but only the first of 3) that was built on June 20th, and June 21st was the first day of summer that year, but neither of those seem like good reasons to pick this date in particular.

Seconding Convox. It's also worth noting that the tooling is open-source, and they profit off an optional-to-use closed-source web interface which has free and paid tiers.

I'm one of two developers at a very young startup, and the one responsible for backend + devops stuff. I simply don't have the time to learn a more complex tool like Kubernetes (not that I didn't consider it) while also working on the actual product. Its simplicity has been a bit limiting on occasion, but they're happy to accept PRs for well thought out changes. I recently had a PR merged regarding UDP ports and ELBs that should make microservice architectures much easier and cheaper to implement.

...I did read the article, what do ALBs have anything to do with what I said? Or are you just assuming that no one needs non-HTTP services running in a VPC load balanced over IPv6?

Unless something has changed since I just happened to have checked earlier today, VPC ELBs are still IPv4-only. They return AAAA records on the ipv6 and dualstack subdomains like their classic/non-VPC counterparts (which do fully support IPv6), but the ports aren't open on the returned addresses, so it's not very useful. Maybe someone from Amazon can chime in?

There are only a handful of actual commits on the repo: two from 1995, and the rest from 4 days ago. It would seem that someone had a tarball of the source and specifically choose to backdate the commit, for whatever reason.

> If you're new to AWS but know Docker (like me) then Docker for AWS seems like a winner.

I'd disagree. It seems you still need to know AWS well enough to setup the various prerequisites. If you're new to AWS but know Docker, you're far better off with something like Convox (which does support docker-compose files)