| #!/usr/bin/env bash | |
| find . -iname "*.m3u*" -exec yt-dlp --enable-file-urls file://$PWD/{} \; | |
| # same as above with subshell | |
| find * -iname '*.m3u*' -print -exec sh -c 'yt-dlp --enable-file-urls "file://$PWD/${1}"' _ {} \; |
| #!/bin/sh | |
| # Remove the performance overlay, it meddles with some tasks | |
| unset LD_PRELOAD | |
| ## Shadow kwin_wayland_wrapper so that we can pass args to kwin wrapper | |
| ## whilst being launched by plasma-session | |
| mkdir $XDG_RUNTIME_DIR/nested_plasma -p | |
| cat <<EOF > $XDG_RUNTIME_DIR/nested_plasma/kwin_wayland_wrapper | |
| #!/bin/sh |
| /** @arg {NS} ns **/ | |
| export async function main(ns) { | |
| ns.disableLog("ALL"); | |
| const scripts = ["/bin/hack.js", "/bin/weak.js", "/bin/grow.js", "/bin/weak.js"]; | |
| const killAllScripts = function(ns, pids) { | |
| for (let index = 0; index < pids.length; ++index) { | |
| for (let i = 0; i < 4; ++i) { ns.kill(pids[index][i]); } | |
| } | |
| } |
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
- Add a filter to git config by running the following command in bash inside the repo:
git config filter.strip-notebook-output.clean 'jupyter nbconvert --ClearOutputPreprocessor.enabled=True --to=notebook --stdin --stdout --log-level=ERROR'
-
Create a
.gitattributesfile inside the directory with the notebooks -
Add the following to that file:
WARNING: Article moved to separate repo to allow users contributions: https://github.com/raysan5/custom_game_engines
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like [Unreal](https:
| /* | |
| Copy this into the console of any web page that is interactive and doesn't | |
| do hard reloads. You will hear your DOM changes as different pitches of | |
| audio. | |
| I have found this interesting for debugging, but also fun to hear web pages | |
| render like UIs do in movies. | |
| */ | |
| const audioCtx = new (window.AudioContext || window.webkitAudioContext)() |
| ============================================== | |
| Factorio Computer V2 Specifications | |
| ============================================== | |
| TABLE OF CONTENTS | |
| 1. Basic Specifications | |
| 1.1 Guidelines | |
| 1.2 Register File | |
| 1.3 ALU |

