| /* compile with: | |
| on linux: gcc -g stack_traces.c | |
| on OS X: gcc -g -fno-pie stack_traces.c | |
| on windows: gcc -g stack_traces.c -limagehlp | |
| */ | |
| #include <signal.h> | |
| #include <stdio.h> | |
| #include <assert.h> |
#Steps to install latest Laravel, LEMP on AWS Ubuntu 16.4 version. This tutorial is the improvised verision of this tutorial on Digitalocean based on my experience.
Run the following commands in sequence.
sudo apt-get install -y language-pack-en-base
sudo LC_ALL=en_US.UTF-8 add-apt-repository ppa:ondrej/php
sudo apt-get update
sudo apt-get install zip unzip
| (function(){ | |
| var newscript = document.createElement('script'); | |
| newscript.type = 'text/javascript'; | |
| newscript.async = true; | |
| newscript.src = 'https://www.gstatic.com/firebasejs/3.0.2/firebase.js'; | |
| (document.getElementsByTagName('head')[0]||document.getElementsByTagName('body')[0]).appendChild(newscript); | |
| })(); | |
| _setFormData = function setFormData (sel, data) { | |
| console.info('setting form to data', data); |
| // gcc -o test init_window.c -I. -lwayland-client -lwayland-server -lwayland-client-protocol -lwayland-egl -lEGL -lGLESv2 | |
| #include <wayland-client.h> | |
| #include <wayland-server.h> | |
| #include <wayland-client-protocol.h> | |
| #include <wayland-egl.h> // Wayland EGL MUST be included before EGL headers | |
| #include "init_window.h" | |
| #include "log.h" | |
| #include <string.h> |
| #include <SDL2/SDL.h> | |
| #include <SDL2/SDL_syswm.h> | |
| #include <bgfx/bgfx.h> | |
| #include <bgfx/platform.h> | |
| #include <bx/bx.h> | |
| #include <bx/mutex.h> | |
| #include <bx/thread.h> | |
| void threadInit() | |
| { |
| #!/usr/bin/env python3 | |
| # | |
| # MDS to standard MIDI file converter | |
| # | |
| # see also http://www.vgmpf.com/Wiki/index.php?title=MDS | |
| # | |
| import argparse | |
| import io | |
| import struct | |
| from typing import BinaryIO, List, Optional |
| #include <X11/Xlib.h> | |
| #include <X11/Xutil.h> | |
| #include <X11/Xos.h> | |
| #include <stdlib.h> | |
| #include <stdio.h> | |
| #include <locale.h> | |
| #include <assert.h> | |
| Display *dpy; | |
| Window win; |
| public class Entity { | |
| public void applyEntityCollision(Entity other) { | |
| double dx = other.posX - this.posX; | |
| double dz = other.posZ - this.posZ; | |
| double largestDistance = Math.max(Math.abs(dx), Math.abs(dz)); | |
| if (largestDistance >= 0.01) { | |
| double vx = dx / 20; | |
| double vz = dz / 20; | |
| if (largestDistance < 1) { |
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to
