Robert Setter sombraguerrero

## gist:ef729eb0a0989761c2838123feef96f4
83, 97, 108, 116, 101, 100, 95, 95
0x53, 0x61, 0x6C, 0x74, 0x65, 0x64, 0x5F, 0x5F
U2FsdGVkX18=

## tsql_join.txt
Joins in T-SQL are optimized such that one table is loaded into memory while the other is dumped to disk.

## clsid.html
<style>
table, tr, td {
	border: 2px solid;
	border-collapse:collapse
}
</style>
<div ><table  width="100%"><tr valign="top"  style="background-color: #CCCCCC"><TD><font size="4"><b>Opens</b></font></TD>
<TD><font size="4"><b>CLSID key (GUID) shortcut</b></font></TD>
</tr>
<tr valign="top" ><TD><font color="#ff0000">3D Objects</font> (folder)</TD>

## ruffle_desktop_linux
Dependencies to build Ruffle desktop on Ubuntu:
* libasound2-dev
* libxcb-shape0-dev
* libxcb-xfixes0-dev
* libgtk-3-dev *libssl-dev
* libxcb-xinput-dev
* libxcb-xkb-dev
* libxcb-cursor-dev*
* default-jre-headless
* cmake

## Pop_os
# Dual Boot Pop!_OS with Windows using systemd-boot
### The ultimate guide for any combination

**EXTREMEY SHORT TL:DR**: If you know what you're doing - The absolute quickest:

1. ```sudo apt install os-prober```
2. ```sudo os-prober```. The output is ```/dev/sdb1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi```
3. ```sudo mount /dev/sdb1 /mnt``` (you can find your drive in the first part of the os-prober's output)
4. ```sudo cp -ax /mnt/EFI/Microsoft /boot/efi/EFI``` (you can find the folder after the word ```efi``` in os-prober's output. It's always ```Microsoft``` but you need capital ```EFI``` when copying.
5. Reboot. Spam your spacebar for the menu. Select with arrows, add timeout with "t" or reduce with "T" (+/- also work), select default with "d". Hold "l" to boot linux after POST or "w" to boot Windows after POST without visiting the menu.

## wasm_build_notes
A note on receivng build errors related to WASM

I resolved this by cleaning up the environment with various permutations of the following:

cargo uninstall wasm-bindgen-cli (the primarily offending crate)
cargo clean (to delete the target folder entirely
npm clean-install (from the web directory of the master source code)
The main thing post-cleanup is to make sure that whatever version of wasm-bindgen-cli was used in the master branch's binding is the one that gets reinstalled before running npm run bootstrap and npm run build again. As of this writing, the last version used was 0.2.69. (cargo install wasm-bindgen-cli --version 0.x.x)
	83, 97, 108, 116, 101, 100, 95, 95
	0x53, 0x61, 0x6C, 0x74, 0x65, 0x64, 0x5F, 0x5F
	U2FsdGVkX18=
	<style>
	table, tr, td {
	border: 2px solid;
	border-collapse:collapse
	}
	</style>
	<div ><table width="100%"><tr valign="top" style="background-color: #CCCCCC"><TD><font size="4"><b>Opens</b></font></TD>
	<TD><font size="4"><b>CLSID key (GUID) shortcut</b></font></TD>
	</tr>
	<tr valign="top" ><TD><font color="#ff0000">3D Objects</font> (folder)</TD>
	Dependencies to build Ruffle desktop on Ubuntu:
	* libasound2-dev
	* libxcb-shape0-dev
	* libxcb-xfixes0-dev
	* libgtk-3-dev *libssl-dev
	* libxcb-xinput-dev
	* libxcb-xkb-dev
	* libxcb-cursor-dev*
	* default-jre-headless
	* cmake
	# Dual Boot Pop!_OS with Windows using systemd-boot
	### The ultimate guide for any combination

	EXTREMEY SHORT TL:DR: If you know what you're doing - The absolute quickest:

	1. ```sudo apt install os-prober```
	2. ```sudo os-prober```. The output is ```/dev/sdb1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi```
	3. ```sudo mount /dev/sdb1 /mnt``` (you can find your drive in the first part of the os-prober's output)
	4. ```sudo cp -ax /mnt/EFI/Microsoft /boot/efi/EFI``` (you can find the folder after the word ```efi``` in os-prober's output. It's always ```Microsoft``` but you need capital ```EFI``` when copying.
	5. Reboot. Spam your spacebar for the menu. Select with arrows, add timeout with "t" or reduce with "T" (+/- also work), select default with "d". Hold "l" to boot linux after POST or "w" to boot Windows after POST without visiting the menu.
	A note on receivng build errors related to WASM

	I resolved this by cleaning up the environment with various permutations of the following:

	cargo uninstall wasm-bindgen-cli (the primarily offending crate)
	cargo clean (to delete the target folder entirely
	npm clean-install (from the web directory of the master source code)
	The main thing post-cleanup is to make sure that whatever version of wasm-bindgen-cli was used in the master branch's binding is the one that gets reinstalled before running npm run bootstrap and npm run build again. As of this writing, the last version used was 0.2.69. (cargo install wasm-bindgen-cli --version 0.x.x)