- Visit https://www.msys2.org/
- Click on the link next to "Download the installer"
- Run the installer
- Add "C:\msys64\usr\bin" to path
// This is a script to retrieve the child processes pids of a process (retrieve the complete process tree) | |
// Tn this example the process identified by pid 7400 is used | |
// (please to run the test chose a process pid that has at least 1 child process) | |
// (tested on windows) | |
package main | |
import ( | |
"fmt" | |
"syscall" |
This is inspired by https://fasterthanli.me/blog/2020/a-half-hour-to-learn-rust/
the command zig run my_code.zig
will compile and immediately run your Zig
program. Each of these cells contains a zig program that you can try to run
(some of them contain compile-time errors that you can comment out to play
with)
package main | |
import ( | |
"context" | |
"flag" | |
"log" | |
"net/http" | |
"os" | |
"os/signal" | |
"time" |
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 everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
The Wayland project seems to operate like they were starting a greenfield project, whereas at the same time they try to position Wayland as "the X11 successor", which would clearly require a lot of thought about not breaking, or at least providing a smooth upgrade path for, existing software.
In fact, it is merely an incompatible alternative, and not e
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 |
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.
Thanks to /u/zpoo32 for reporting several issues in this list!
- deemix: just the cli and the library
- deemix-pyweb: the app with a GUI
- deemix-server: just the server part of deemix-pyweb
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; | |
} |
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
.