Hello Diablo community, welcome to another Diablo 4 Campfire Chat. My name is Adam Fletcher, I am the Associate Director of Community here for Diablo. I'm joined here by Joe Shelley, Game Director of Diablo 4, and Mr. Joe Paipora, the Associate Game Director for Diablo 4. We have a lot to talk about today. Obviously we have this Campfire Chat because we do want to talk about the patch that just released this past week, which is patch 1.1.0. We've seen a ton of feedback, we've heard a lot of feedback, and so we do want to go through a lot of the points of feedback that we've been hearing and at the same time the patch itself. The biggest thing to kick us off here, I think we want to obviously acknowledge everyone's feedback in regards to reducing player power. We know it is bad, we know it is not fun, and it's something that we ourselves know that it's not the greatest play experience for players out there. We do want to explain why we ended up doing it within the actual patch, and then of course we also want |
https://www.chronophoto.app/web.html | Chronophoto - The Photographical History Game | |
https://maxbittker.github.io/broider/ | broider | |
https://www.searchthedeck.com/ | Search The Deck | |
https://news.ycombinator.com/item?id=34531989 | Ask HN: What have you created that deserves a second chance on HN? | Hacker News | |
https://www.coursera.org/learn/modernrobotics-course1/supplement/htN7x/welcome-to-the-specialization | Welcome to the Specialization! | Coursera | |
http://hades.mech.northwestern.edu/index.php/Modern_Robotics | Modern Robotics - Northwestern Mechatronics Wiki | |
https://pypi.org/project/modern_robotics/ | modern_robotics · PyPI | |
https://beagleboard.org/blue | BeagleBoard.org - blue | |
https://odriverobotics.com/ | ODrive | |
https://datasette.io/examples | Datasette Examples |
with open('onetab.txt', encoding="utf-8") as f: | |
with open('dedup.txt', 'w', encoding="utf-8") as out: | |
links = {} | |
is_linebreak = False | |
for line in f: | |
line = line.strip() | |
if not line: | |
if not is_linebreak: | |
out.write('\n') | |
is_linebreak = True |
#!/bin/sh | |
# From https://stackoverflow.com/a/28319271 | |
set -e | |
if [ $# -eq 0 ]; then | |
dir="." | |
else | |
dir="$1" |
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.
This gist will collects all issues we solved with Rails 5.2 and Webpacker
# Last few parameters(--skip-* part) is only my habbit not actully required
$ rails new <project_name> --webpack=stimulus --database=postgresql --skip-coffee --skip-test
# vi: ft=dosini | |
[main] | |
# Enables context sensitive auto-completion. If this is disabled the all | |
# possible completions will be listed. | |
smart_completion = True | |
# Display the completions in several columns. (More completions will be | |
# visible.) | |
wider_completion_menu = False |
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
# custom PyCharm Community Edition VM options | |
# https://intellij-support.jetbrains.com/hc/en-us/articles/206544869?page=1#comment_200744859 | |
-ea | |
-server | |
-Xms1g | |
-Xmx1g | |
-Xss16m | |
-XX:PermSize=256m | |
-XX:MaxPermSize=256m |