| SOLARIZED | HEX | 16/8 | TERMCOL | XTERM | HEX | L*A*B |
RGB | HSB | GNU screen |
|---|---|---|---|---|---|---|---|---|---|
| base03 | #002b36 | 8/4 | brblack | 234 | #1c1c1c | 15,-12,-12 |
0,43,54 |
193,100,21 |
K |
| base02 | #073642 | 0/4 | black | 235 | #262626 | 20,-12,-12 |
7,54,66 |
192,90,26 |
k |
| base01 | #586e75 | 10/7 | brgreen | 240 | #585858 | 45,-07,-07 |
88,110,117 |
194,25,46 |
G |
| base00 | #657b83 | 11/7 | bryellow | 241 | #626262 | 50,-07,-07 |
101,123,131 |
195,23,51 |
Y |
| base0 | #839496 | 12/6 | brblue | 244 | #808080 | 60,-06,-03 |
131,148,150 |
186,13,59 |
B |
| base1 | #93a1a1 | 14/4 | brcyan | 245 | #8a8a8a | `65,-05 |
| crypto = require('crypto'); | |
| #Quick MD5 of text | |
| text = "MD5 this text!" | |
| md5hash1 = crypto.createHash('md5').update(text).digest("hex") | |
| #MD5 of text with updates | |
| m = crypto.createHash('md5') | |
| m.update("MD5 ") | |
| m.update("this ") |
I recently switched over to neovim (see my screenshots at the bottom). Below is my updated config file.
It's currently synchronized with my .vimrc config except for a block of neovim-specific terminal key mappings.
This is still a work in progress (everyone's own config is always a labor of love), but I'm already extremely pleased with how well this is working for me with neovim. While terminal mode isn't enough to make me stop using tmux, it is quite good and I like having it since it simplifies my documentation workflow for yanking terminal output to paste in a markdown buffer.
These days I primarily develop in Go. I'm super thrilled and grateful for fatih/vim-go,
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.
There exist several DI frameworks / libraries in the Scala ecosystem. But the more functional code you write the more you'll realize there's no need to use any of them.
A few of the most claimed benefits are the following:
- Dependency Injection.
- Life cycle management.
- Dependency graph rewriting.