HN user
This article disagrees with you:
https://foreignpolicy.com/2018/09/25/taiwan-can-win-a-war-wi...
Both Westerners and Taiwanese should be more optimistic about the defense of Taiwan than is now normal.
Yes, the Taiwanese Army projects that it can only hold off its enemy for two weeks after the landing—but the PLA also believes that if it cannot defeat the Taiwanese forces in under two weeks, it will lose the war!
Looks like they somehow converted the hyphens to underscores: https://hired.com/state-of-salaries-2017
Yes, this is my biggest problem with the autoscaler as well. I opened an issue about this almost a year ago, looks like they're finally getting around to addressing it: https://github.com/kubernetes/autoscaler/pull/77
To expand on the sibling comment by nrmitchi, in Kubernetes you don't scale your worker nodes by CPU or memory. Instead you scale your pods by CPU or memory. Running the cluster autoscaler ensures that when you run out of space to schedule a new pod new worker nodes are brought up. It also works the other way; when your nodes are being underutilized for a while, the autoscaler will kill some nodes (and the scheduler will automatically handle placing any pods on those nodes onto other nodes).
You still can't use Curator to take snapshots, because AWS ES doesn't expose the `/_snapshot/_status` endpoint.
You can use Route53 for just a subdomain even if your parent domain is not done through Route53, see https://github.com/kubernetes/kops/blob/master/docs/creating...
That's only if you use VPC networking. If you use external networking, you can deploy a networking Daemonset (Weave, Flannel, etc.) and there's no 50 node limit.
I tried Weave but ultimately had to abandon it, as there were too many issues in resolving DNS directly to containers. Kubernetes resolves DNS to a virtual IP that in turns maps to the container IPs, which I found to be a much better approach.
This is a relatively recent development and certainly wasn't true for most of Ashkenazi history.
Very cool!
On page 17 of the Solar System book I want to rotate the globe but can't manage to do that without also initiating a page flip, which is pretty annoying.
Also, the formula rendering on page 21 is not quite right (Firefox).
I think that non-nullable types by default are one of Dart's biggest missed opportunities, so I'm really hoping that the Dart team ends up adopting this.
This is also a really great example of the DEP system in action. DEPs (Dart Enhancement Proposals) allow anyone to suggest improvements to the Dart platform, and work with the Dart team to determine if it can be accepted and implemented. This means that individual community members can advance the language forward and that's exactly what's happening here. The author of the proposal, Patrice Chalin, is not on the Dart team but that hasn't stopped him from creating an awesome proposal that has earned praise from Dart team members.
Very cool concept!
I spent a while tweaking the code to get more CPU cycles, but after a while tired of mining the asteroids manually, so I just got rid of them:
ENGINE.Game.spawnAsteroid = function () {}
SHIP_CPU_COST = 0.001;
Regarding targeting the web, you can't do this directly with RoboVM, but you can use GWT to do so. This means that you can target Android, iOS, and web with Java. You would have shared code that all platforms could use, and then build the UIs natively.
This is pretty much the approach that Google use with Inbox, except they used j2objc instead of RoboVM.