Some notes on Audio pitch correction (eg. autotune, melodyne, etc).
// ==UserScript== | |
// @name Remove Twitter Blue Promotions | |
// @namespace https://d23.dev/ | |
// @version 1.1 | |
// @description Removes the "Get Verified" box on the Home page and the "Verified" button on the sidebar | |
// @author angeld23 | |
// @match *://*.twitter.com/* | |
// @icon https://www.google.com/s2/favicons?sz=64&domain=twitter.com | |
// @grant none | |
// ==/UserScript== |
This excercise is intended for candidates for PhD students in COeXISTENCE
Please send the solution reports to [email protected]
#!/bin/ash | |
# list installed packages sorted by file size | |
apk info -e -s \* >/tmp/apksize | |
awk 'NR % 3 == 1' /tmp/apksize | cut -d ' ' -f 1 > /tmp/apkname | |
awk 'NR % 3 == 2' /tmp/apksize > /tmp/apksize2 | |
while read -r n unit; do | |
B=$n | |
case "$unit" in |
module corescore_emitter_uart | |
#( | |
parameter clk_freq_hz = 0, | |
parameter baud_rate = 57600) | |
( | |
input wire i_clk, | |
input wire i_rst, | |
input wire [7:0] i_data, | |
input wire i_valid, | |
output reg o_ready, |
name: bbcsdl | |
base: core20 | |
version: "master" | |
summary: BBC BASIC for SDL 2.0 | |
license: "Zlib" | |
description: | | |
BBC BASIC for SDL 2.0 is a cross-platform implementation of the BBC BASIC | |
programming language for Windows, Linux (x86), MacOS, Raspbian (Raspberry Pi), | |
Android, iOS and Emscripten / WebAssembly. It is highly compatible with BBC | |
BASIC for Windows and has the same language extensions, but uses SDL 2.0 as |
Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill
) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
As 2024 is winding down:
At the beginning of 2030, I found this essay in my archives. From what I know today, I think it was very insightful at the moment of writing. And I feel it should be published because it can teach us, Rust developers, how to prevent that sad story from happening again.
What killed Haskell, could kill Rust, too
What killed Haskell, could kill Rust, too. Why would I even mention Haskell in this context? Well, Haskell and Rust are deeply related. Not because Rust is Haskell without HKTs. (Some of you know what that means, and the rest of you will wonder for a very long time). Much of the style of Rust is similar in many ways to the style of Haskell. In some sense Rust is a reincarnation of Haskell, with a little bit of C-ish like syntax, a very small amount.
Is Haskell dead?
module horn_goldilocks_array( | |
height = 2.5, | |
plot = 10, | |
tolerances = [0, .1, .2, .3, .4, .5, .6, .7, .8, .9, 1], | |
shim_counts = [0, 3, 6] | |
) { | |
difference() { | |
cube([ | |
plot * len(tolerances), | |
plot * len(shim_counts), |
As Gecko is moving toward more Rust code, the cases where Rust and C code interoperate will become more common.
This document is an attempt to ease the learning curve for engineers facing it for the first time. It assumes no prior experience with cross-language C interfaces (called FFI).
It also assumes that Rust code is already built into Gecko. If you need help with that, read Introducing Rust code in Firefox.