679 karma · joined September 28, 2010
I don't want to call you out but in https://c9.io/blog/content/images/2015/07/recursion.png you're really only running C9 in C9 - the rest have the same URL.
I feel like IFTTT is our best bet, while it doesn't do the "Unix pipe" that pipes offered it at least provides some usability to the process.
http://www.theverge.com/2015/5/26/8662905/the-verge-and-reco...
Also you've shown a comparison between a first generation device and first generation device, what is particularly wrong with the watch?
I imagine this reduces complexity and lets them increase their throughput of uploads but I wonder if 500px toyed around with the idea of first uploading it to local (temp) storage, having the workers process it and then finally persist it. But I guess the cons are a) some point it needs to go to S3 in original form b) increases data loss
If you're not familiar with the OS' terminal, dependencies or installers then those are just additional barriers to getting down to programming. With a prepared development environment for say Rails or Meteor you can get started very quickly learning to develop with these frameworks.
For some development environments it was previously a pain on Windows, while this has changed for Meteor it's still not as friendly for Rails. If you can offload those problems to a hosted environment that's a big win.
But regardless you should be locking down access to the SQL host by network ranges, but I'm not sure if all providers have that ability.
They flooded the Facebook pages of both stores with angry comments; some even called in death threats, according to a video later posted by Andy Raymond, an owner of Engage Armament.
Thank god they are the ones with guns....With tug any port you expose on the containers is brought locally to you instantly.
I wouldn't describe tug as less powerful, it's less complicated from my usage of it. For each service I only need to write one line and tug will figure out (from the Dockerfile) what needs to be forwarded.
The mind blowing moment is when you're using boot2docker (or any case where Docker isn't local) and it still forwards the ports to your local (127.0.0.1) host.
If they mess up the API calls, they can sidetrack the review process and deliver a swift update.
Maybe Apple aren't confident with UIPopovers on iPhone and are awaiting its maturity until they let it loose. I highly doubt holding back a popover would be malice on Apple's part.
EDIT: Imagine if Apple released APIs as soon as they used them, we'd see more blog posts complaining about the reliability of an API they were promised.
But by the looks of it the library bundles in the adapters to talk directly to these worker frameworks (currently it only is Resque). Are we going to see an active merging in of adapters or will at some point will the response be 'we won't be allowing any more adapters to bundled'.
Not sure what reliable hosting providers through in database for free and expect it handle 3600+ connections.
* You treated the system's memory like it was some infinite resource. It's not, you need to make sure your application efficiently handles memory and takes measure to ensure it doesn't grow too large. Would you want it swapping on a regular host?
* You thought you could get away with a free database that is used for development.
You're using an application that isn't built well for shared environments, it expects dedicated hosting.
You'd be better off designing your blog around Azure Web Sites, knowing the advantages and disadvantages of the platform and taking advantage of them. Don't try to shoehorn it in.