When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:
main {
max-width: 38rem;
padding: 2rem;
margin: auto;
}| #!/bin/bash | |
| # btrfs-undelete | |
| # Copyright (C) 2013 Jörg Walter <[email protected]> | |
| # This program is free software; you can redistribute it and/or modify it under | |
| # the term of the GNU General Public License as published by the Free Software | |
| # Foundation; either version 2 of the License, or any later version. | |
| if [ ! -b "$1" -o -z "$2" -o -z "$3" ]; then | |
| echo "Usage: $0 <dev> <file/dir> <dest>" 1>&2 | |
| echo |
| #!/bin/bash | |
| # This script will make a best-effort attempt at showing modifications | |
| # to package-provided config files on a Debian system. | |
| # | |
| # It's subject to some pretty significant limitations: most notably, | |
| # there's no way to identify all such config files. We approximate the | |
| # answer by looking first at dpkg-managed conffiles, and then hoping | |
| # that most of the time, if maintainer scripts are managing files | |
| # themselves, they're using ucf. So, DO NOT TRUST THIS SCRIPT to find |
Just documenting docs, articles, and discussion related to gRPC and load balancing.
https://github.com/grpc/grpc/blob/master/doc/load-balancing.md
Seems gRPC prefers thin client-side load balancing where a client gets a list of connected clients and a load balancing policy from a "load balancer" and then performs client-side load balancing based on the information. However, this could be useful for traditional load banaling approaches in clound deployments.
https://groups.google.com/forum/#!topic/grpc-io/8s7UHY_Q1po
gRPC "works" in AWS. That is, you can run gRPC services on EC2 nodes and have them connect to other nodes, and everything is fine. If you are using AWS for easy access to hardware then all is fine. What doesn't work is ELB (aka CLB), and ALBs. Neither of these support HTTP/2 (h2c) in a way that gRPC needs.
| #!/bin/bash | |
| # | |
| # Based upon [[https://superuser.com/questions/1268732/how-to-hide-tab-bar-tabstrip-in-firefox-57-quantum/1268734#1268734][How to hide tab bar (tabstrip) in Firefox 57+ Quantum]] by [[https://superuser.com/users/162466/vasyanovikov][VasyaNovikov]] | |
| # This causes the [[https://support.mozilla.org/en-US/questions/1187186][The Back Button is top right under the Red close button on my Mac]] issue. | |
| # Resolve that by right-clicking the toolbar, then inserting three Flexible Space into the toolbar on the far-left-hand side. | |
| case $( uname ) in | |
| "Linux") | |
| profile_dir=~/.mozilla/firefox/$( ls -tr ~/.mozilla/firefox/ | grep -v profiles.ini | tail -1 ) | |
| ;; | |
| "Darwin") |
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
Copyright © 2016-2018 Fantasyland Institute of Learning. All rights reserved.
A function is a mapping from one set, called a domain, to another set, called the codomain. A function associates every element in the domain with exactly one element in the codomain. In Scala, both domain and codomain are types.
val square : Int => Int = x => x * x| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |