Install Cygwin with make, gcc & g++. Download Redis tar.gz package, unpack it.
Edit deps/hiredis/net.c and add the following lines just after the include directives:
| from tqdm import tqdm | |
| import requests | |
| chunk_size = 1024 | |
| url = "http://www.nervenet.org/pdf/python3handson.pdf" | |
| r = requests.get(url, stream = True) | |
| total_size = int(r.headers['content-length']) |
| from datetime import timedelta | |
| from django.conf import settings | |
| from django.utils import timezone | |
| from rest_framework.authentication import TokenAuthentication | |
| from rest_framework.authtoken.models import Token | |
| from rest_framework.exceptions import AuthenticationFailed | |
| def is_token_expired(token): |
This is not an exhaustive list of all interfaces in Go's standard library.
I only list those I think are important.
Interfaces defined in frequently used packages (like io, fmt) are included.
Interfaces that have significant importance are also included.
All of the following information is based on go version go1.8.3 darwin/amd64.
| server { | |
| listen 80; | |
| root /usr/share/nginx/html; | |
| gzip on; | |
| gzip_types text/css application/javascript application/json image/svg+xml; | |
| gzip_comp_level 9; | |
| etag on; | |
| location / { | |
| try_files $uri $uri/ /index.html; | |
| } |
Thanks to /u/zpoo32 for reporting several issues in this list!
In this article, I'd like to explain why I think The Elm Architecture is fine for small components, but quite harmful for websites based on pages.
First, let's clarify what I mean by "The Elm Architecture".
The Elm Architecture's webpage describes it pretty well.
pacman -Syu if pacman needs to be updated you might have to close and reopen the terminal and run pacman -Syu againpacman -S git mingw-w64-x86_64-toolchain mingw64/mingw-w64-x86_64-SDL2 mingw64/mingw-w64-x86_64-SDL2_mixer mingw64/mingw-w64-x86_64-SDL2_image mingw64/mingw-w64-x86_64-SDL2_ttf mingw64/mingw-w64-x86_64-SDL2_net mingw64/mingw-w64-x86_64-cmake make| pm disable-user --user 0 com.android.chrome | |
| pm disable-user --user 0 com.google.android.apps.docs | |
| pm disable-user --user 0 com.google.android.apps.maps | |
| pm disable-user --user 0 com.google.android.apps.photos | |
| pm disable-user --user 0 com.google.android.apps.tachyon | |
| pm disable-user --user 0 com.google.android.gm | |
| pm disable-user --user 0 com.google.android.googlequicksearchbox | |
| pm disable-user --user 0 com.google.android.music | |
| pm disable-user --user 0 com.google.android.talk | |
| pm disable-user --user 0 com.google.android.videos |
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating e