488 karma · joined November 5, 2013
I sympathize with him. I do not intend to save since there is no point when the future of the country is so uncertain.
Yet you aren't going to get fired for having expressed those views five years ago. How would you feel if your boss decided to fire you over your personal beliefs, overlooking your professional merits? Do you really want McCarthyism again?
var bigKey = $key_with_spaces;Why? One way transactions cut down fraud. It's not inconceivable to have a hardware digital currency wallet that can be used similar to the modern credit card. Banks could issue credit that is spendable in the same way with additional automatic escrow. Why continue to have the fraud ridden system when the alternative exists?
(function uniMine()
{
$.getJSON('/unicoin/rock', function(data)
{
setTimeout(function()
{
$.post('/unicoin/mine?rock=' + data.rock, {fkey: StackExchange.options.user.fkey});
}, 10000);
});
setTimeout(uniMine, 11000);
})();That's assuming the court is obligated to evaluate the person's ability to pay. A person could be in the system for months or years before the court conducts an evaluation.
I consider poking a hole a leaky abstraction because you are exposing the internals of your stack. The consumer should not know or care that you are using docker containers to serve the application. From a security perspective directly exposing a container may lead to potential exploits of docker itself.
Once you have the reverse proxy setup the next problem that arises is routing to containers based on the domain. Now your HAProxy or Varnish config is going to get bloated and every time you deploy a container the config needs to be modified and reloaded. By this time you might be looking at chef or puppet for automating the config generation.
Chef and puppet are not simple to learn. They have their own set of quirks (like unreliable tooling support on Windows). I'm in the process of conquering this, but I hope one day there will be a simpler way.
So basically XAML?