679 karma · joined September 28, 2010
I'd argue the system this sort of replaces, bank numbers + account numbers, was still better than the US. It provided next day transfer between banks and intra day transfers between the same bank. All for free.
Hopefully they’ll make it easier with their Kubernetes integration.
Running a Docker container in production is not a 20 minute job.
I thought it now depends on the firmware in the card readers, which it seems companies like Index control.
Didn't expect Chess.com and YouTube to have a crossover of users? Surprised there isn't active moderation on a site this size.
My argument probably isn't as valid but I still think the guarantee of 2 iPhone generations is safer than the fragmentation of Android devices that would be "released in the past 2 years".
They are apples and oranges and the point is that the iPhone for a few years back is a guaranteed hardware specification that you can guarantee ARKit will work on. If you think about this for Android, you'd need to slice it by the devices that are compatible - it's not going to be a guarantee by OS.
Sadly it looks like this is read-only, which would eliminate companies like Clipper from implementing it?
I call B.S. on this. Amazon wouldn't have spent so much effort on ECS if this was true.
It definitely sounds like Swarm is not ready but I wouldn't say this is representative of running Docker in production: instead you should be running one of the many battle tested cluster tools like ECS, Mesos or Kubernetes (or GCE).
I love Go and used it to build some very useful web hook and CLI tools. It just doesn't lend itself to something where you expect to have a vast set of APIs under one Go project.
User uploads a provided PNG, you perform the quickest compression compression but then queue up a Zopfli compression. Up front you're only returning the less compressed file but after time you begin serving up the lesser bandwidth file.
If the uploaded file or associated post is deleted then you can wipe it from the queue.