| #!/bin/bash | |
| # Install opus-tools | |
| # Latest releases: opus 1.3.1, opus-tools 0.2, opusfile 0.11, libopusenc 0.2.1 | |
| set -e | |
| set -o pipefail | |
| # Install packages needed | |
| apt update > /dev/null 2>&1 && apt install -y curl libflac-dev > /dev/null 2>&1 |
| For 32-bit cygwin see current description on web page, | |
| http://www.mono-project.com/docs/compiling-mono/windows. Bellow instructions apply to 64-bit cygwin | |
| building 32 and 64-bit mono using mingw. | |
| Install prerequisite: | |
| • A working GIT environment is assumed (GIT can also be installed using chocolatey if needed). | |
| • Visual Studio 2015. |
My friend Michael Jackson turned off github issues on one of his smaller projects. It got me thinking...
Maintainers getting burned out is a problem. Not just for the users of a project but the mental health of the maintainer. It's a big deal for both parties. Consumers want great tools, maintainers want to create them, but maintainers don't want to be L1 tech support, that's why they
Format text with nothing but Unicode symbols. (Partially supported in Chrome)
| Style | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Uppercase, Sans, Regular |
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
Lowercase, Sans, Regular |
a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | p | q | r | s | t | u | v | w | x | y | z |
Uppercase, Serif, Regular |
𝐀 | 𝐁 | 𝐂 | 𝐃 | 𝐄 | 𝐅 | 𝐆 | 𝐇 | 𝐈 | 𝐉 | 𝐊 | 𝐋 | 𝐌 | 𝐍 | 𝐎 | 𝐏 | 𝐐 | 𝐑 | 𝐒 | 𝐓 | 𝐔 | 𝐕 | 𝐖 | 𝐗 | 𝐘 | 𝐙 |
Lowercase, Serif, Regular |
𝐚 | 𝐛 | 𝐜 | 𝐝 | 𝐞 | 𝐟 | 𝐠 | 𝐡 | 𝐢 | 𝐣 | 𝐤 | 𝐥 | 𝐦 | 𝐧 | 𝐨 | 𝐩 | 𝐪 | 𝐫 | 𝐬 | 𝐭 | 𝐮 | 𝐯 | 𝐰 | 𝐱 | 𝐲 | 𝐳 |
| // ==UserScript== | |
| // @name PPCG Design | |
| // @namespace Doᴡɴɢᴏᴀᴛ | |
| // @version 1 | |
| // @author Doᴡɴɢᴏᴀᴛ | |
| // @grant none | |
| // ==/UserScript== | |
| function qS(x){ | |
| return document.querySelector(x); |
| // ==UserScript== | |
| // @name favicon | |
| // @namespace Cᴏɴᴏʀ O'Bʀɪᴇɴ | |
| // @version 1 | |
| // @grant none | |
| // ==/UserScript== | |
| function qS(x){ | |
| return document.querySelector(x); | |
| } |
| 67010 AQ | |
| 67012 AQ | |
| 67013 AQ | |
| 67014 AQ | |
| 67015 AQ | |
| 67017 AQ | |
| 67019 AQ | |
| 67020 AQ | |
| 67021 AQ | |
| 67022 AQ |
| // Creating a node graph editor for Dear ImGui | |
| // Quick sample, not production code! | |
| // This is quick demo I crafted in a few hours in 2015 showcasing how to use Dear ImGui to create custom stuff, | |
| // which ended up feeding a thread full of better experiments. | |
| // See https://github.com/ocornut/imgui/issues/306 for details | |
| // Fast forward to 2023, see e.g. https://github.com/ocornut/imgui/wiki/Useful-Extensions#node-editors | |
| // Changelog | |
| // - v0.05 (2023-03): fixed for renamed api: AddBezierCurve()->AddBezierCubic(). |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
Please petition Github to support HTTPS on github pages: https://github.com/contact
Here's what I wrote:
Obviously, a lot of people want HTTPS for github pages:
Until recently, that would be difficult to implement but, as it turns out, the implementation is pretty much complete: