xoxefdp

# https://success.docker.com/article/How_to_completely_remove_Docker_in_Windows_10

$ErrorActionPreference = "SilentlyContinue"

kill -force -processname 'Docker for Windows', com.docker.db, vpnkit, com.docker.proxy, com.docker.9pdb, moby-diag-dl, dockerd

try {
    ./MobyLinux.ps1 -Destroy
} Catch {}

mutin-sa

Google Public NTP [AS15169]:

time.google.com

time1.google.com

time2.google.com

time3.google.com

gaearon

If you haven’t worked with JavaScript in the last few years, these three points should give you enough knowledge to feel comfortable reading the React documentation:

• We define variables with let and const statements. For the purposes of the React documentation, you can consider them equivalent to var.
• We use the class keyword to define JavaScript classes. There are two things worth remembering about them. Firstly, unlike with objects, you don't need to put commas between class method definitions. Secondly, unlike many other languages with classes, in JavaScript the value of this in a method [depends on how it is called](https://developer.mozilla.org/en-US/docs/Web/Jav

Lonami

import struct
import socket
import base64
import json
import sys


class Server:
    def __init__(self, data):
        self.description = data.get('description')

NaniteFactory

package lpcwstr

// #include <windows.h>
// #include <wchar.h>
// #include <WinNT.h>
import "C"

import (
	"unicode/utf16"
	"unsafe"

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

luismts

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

bigwheel

6.8.1 Package Names

Names of packages that are to be made widely available should be formed as described in §7.7. Such names are always qualified names whose first identifier consists of two or three lowercase letters that name an Internet domain, such as com, edu, gov, mil, net, org, or a two-letter ISO country code such as uk or jp. Here are examples of hypothetical unique names that might be formed under this convention:

com.JavaSoft.jag.Oak
org.npr.pledge.driver
uk.ac.city.rugby.game

yougg

// +build windows

//go:generate go build -ldflags "-s -w -extldflags '-static'" $GOFILE
package main

import (
	"fmt"
	"syscall"
	"unsafe"
)

cptpiepmatz

@echo off
rem Version 1.1.1

set picturePath="%UserProfile%\Pictures\GTA Snapmatic"
set convertScript="%UserProfile%\Pictures\GTA Snapmatic\ConvertSnapmaticToJpg.ps1"

md %picturePath%

echo Copying Snapmatic Pictures to Pictures Folder
echo ---------------------------------------------