This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
#!/usr/bin/bash | |
declare -a repos=( | |
"$HOME/Projects/myproject/testing/.git" | |
"$HOME/Projects/myproject/testing-bundle/.git" | |
"$HOME/Projects/myproject/service-skeleton/.git" | |
"$HOME/Projects/myproject/documentation-web/.git" | |
"$HOME/Projects/myproject/documentation-api/.git" | |
"$HOME/Projects/myproject/coding-standard/.git" | |
"$HOME/Projects/myproject/context/microservice1/.git" |
import org.gradle.api.logging.LogLevel; | |
import org.gradle.api.logging.Logging; | |
import org.slf4j.Marker; | |
/** | |
* Created by ahasbini on 11-Oct-19. | |
*/ | |
public class Logger implements org.gradle.api.logging.Logger { | |
private static boolean useQuietLogs = false; |
Questions:
Discourse is very clear that they do not support anything else than their official install instructions, which more or less requires a dedicated server.
For an emulator that mimics a Pixel 5 Device with Google APIs and ARM architecture (for an M1/M2 Macbook):
List All System Images Available for Download: sdkmanager --list | grep system-images
Download Image: sdkmanager --install "system-images;android-30;google_atd;arm64-v8a"
ASP.NET core has a very useful dev-certs
utility capable of producing self-signed certificates for local https development work.
This works for the most-part, but as soon as you start wanting to do local development of a native app, iOS refuses to trust the certificate, or indeed, to even let you tell it to trust it.
You can see This Issue for some more context.
This is what worked for me, I make no guarantees as to its efficiency or ongoing efficacy.
All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.
A number of methods in React are assumed to be "pure".
On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.
edittext.setOnFocusChangeListener(new View.OnFocusChangeListener() { | |
@Override | |
public void onFocusChange(View v, boolean hasFocus) { | |
if (!hasFocus) { | |
Log.d("focus", "focus loosed"); | |
// Do whatever you want here | |
} else { | |
Log.d("focus", "focused"); | |
} | |
} |
# LVDB - LLOOGG Memory DB | |
# Copyriht (C) 2009 Salvatore Sanfilippo <antirez@gmail.com> | |
# All Rights Reserved | |
# TODO | |
# - cron with cleanup of timedout clients, automatic dump | |
# - the dump should use array startsearch to write it line by line | |
# and may just use gets to read element by element and load the whole state. | |
# - 'help','stopserver','saveandstopserver','save','load','reset','keys' commands. | |
# - ttl with milliseconds resolution 'ttl a 1000'. Check ttl in dump! |