We are using many CouchDB servers and I can confirm that we got a heads-up plus a patch several days before the 1.7.0 release. The CouchDB team and the Hoodie team did a great job handling this issue.
Fetching data directly in components is bad advice and leads to a program with cluttered data access becoming more and more unmaintainable as the app grows. You need to encapsulate fetching and storage in redux or a similar state management solution.
When you are using Kubernetes, you won't have to deal with this yourself. The Cluster will move pods from nodes that are stopped because the spot price is exceeded. Ideally place nodes at different bids. So there will be a performance hit but no outage. With the new AWS start/stop feature [1] nodes will come up again when the spot price sinks.
Same happened to me. I "lost" my all my credit. It was not promotional, but something I had paid. They informed me on March 31th that I wouldn't be able to use that credit after May 1st. :-(
P.S. They had no expiration policy in place when I added the credit.
Am I the only one who thinks running scripts on a site directly from npm is a bad idea? What happens when an incompatible change in any of the dependencies is pushed. What if a package owner had transferred his ownership und the new owner pushes whatever he wants.
For example if adding a URL on https://flems.io it will store the xhr.responseURL to take advantage of this to pin the version. I would guess guess Scrimba does something similar?
The risk is real. When some site has a link with _blank to your site, the opener site stays accessible for javascript code that is embedded in your site.
Also interesting are solutions using xpra, especially when are working over a remote connection. In this case you are not running X on the Mac, but a xpra client (a simple app).
There is also the possibility of installing a VNC server inside the container and a desktop environment, then connecting to that. I did this when I wanted MonoDevelop on my Mac without having to install the mandatory 3-5gb of "Xamarin Studio" mobile emulators etc. Btw thanks for the link back to xpra.
