Dima Paloskin dimapaloskin

## renderer.odin
package vendor_wgpu_example_fontstash

import intr "base:intrinsics"

import      "core:fmt"
import      "core:math/linalg"
import sa   "core:container/small_array"

import fs   "vendor:fontstash"
import      "vendor:wgpu"

## nasm_m1.md

      
              1 file
            
          
              1 fork
            
          
                2 comments
              
            
              5 stars
            
          
                n2o
                / nasm_m1.md
            
            
              Last active
              February 17, 2025 19:26
            
              
                Compiling x86_64 assembly program on M1 Mac
              
          
    If you have an M1 Mac and want to compile and execute x86_64 assembly code, make sure you install Rosetta 2 and nasm (brew install nasm).
Than, take a 64 Bit assembly program, e.g. from this tutorial page (https://cs.lmu.edu/~ray/notes/nasmtutorial/) in Section
"Your First Program" for macOS, save it to a file called hello.asm.
Compile, link and execute the program:
nasm -f macho64 hello.asm
ld hello.o -o hello -macosx_version_min 11.0 -L /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib -lSystem

./hello

  
## rust_in_swift.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              22 stars
            
          
                Jomy10
                / rust_in_swift.md
            
            
              Last active
              November 5, 2025 15:49
            
              
                Calling Rust library from Swift code (creating executable)
              
          
    Calling a Rust library from Swift

This gist shows a quick overview of calling Rust in a Swift project, with Swift Package Manager configured.
Let's go ahead and create a folder containing all our sources:
mkdir swift-rs && cd $_

  
## zig_test_debugging_vscode.md

      
              1 file
            
          
              6 forks
            
          
                6 comments
              
            
              24 stars
            
          
                floooh
                / zig_test_debugging_vscode.md
            
            
              Last active
              June 18, 2025 02:11
            
              
                How to debug Zig tests in VSCode
              
          
    Tested on macOS:

Install the CodeLLDB VSCode extension. Unlike the debugger in the C/C++ extension, this allows to set
breakpoints inside Zig "test" blocks (in the MS C/C++ extension debugger, breakpoints inside test blocks
will be disabled once the debugger starts for unknown reasons.
When compiling the test, tell it to also emit a binary: zig test -femit-bin=zig-out/bin/my-test src/bla.zig,
otherwise there will be no executable to debug.
The compiled test executable expects the path to the Zig executable as first command line argument, the launch.json file
needs to be setup accordingly (note the args item):


## update-ffmpeg-rpi.sh
#!/bin/bash

#  #########################################################
#
#  WW      WW   AAA   RRRRRR  NN   NN IIIII NN   NN   GGGG
#  WW      WW  AAAAA  RR   RR NNN  NN  III  NNN  NN  GG  GG
#  WW   W  WW AA   AA RRRRRR  NN N NN  III  NN N NN GG
#   WW WWW WW AAAAAAA RR  RR  NN  NNN  III  NN  NNN GG   GG
#    WW   WW  AA   AA RR   RR NN   NN IIIII NN   NN  GGGGGG
#

## promises.re
/**
 * Making promises
 */
let okPromise = Js.Promise.make((~resolve, ~reject as _) => [@bs] resolve("ok"));

/* Simpler promise creation for static values */
Js.Promise.resolve("easy");

Js.Promise.reject(Invalid_argument("too easy"));

## functions.php
/*
 * Example adds certain named Product Attribute fields to the product Edit screen ready for completion.
 * (Pre-requisite )
 * This saves the Shop Admin having to add them manually.
 *
 * Why might you want to do this instead of adding Custom fields?  There's plenty of nice documentation on adding custom fields
 * for example: http://www.remicorson.com/mastering-woocommerce-products-custom-fields/
 *
 * Well a Product Attributes are a built in WooCommerce feature, using Terms which are a built in Wordpress feature.
 * - no add-ons required

## ArtistList.js
import React from 'react'
import { observer } from 'mobx-react'

function ArtistList({ uiState: { artistData } }) {
  const { data } = artistData;
  if ( !data || !data.artists || !data.artists.length ) {
    return <div>No artists bruh.</div>
  }
  const { artists } = data
  return (

## index.html
<!doctype html>
<html lang="en">
<body>
  <span id="output"></span>
</body>
<script>
(function () {
var workerBlob = new Blob(
    [workerRunner.toString().replace(/^function .+\{?|\}$/g, '')],
    { type:'text/javascript' }

## raspberry-pi-chroot-armv7-qemu.md

      
              1 file
            
          
              10 forks
            
          
                8 comments
              
            
              32 stars
            
          
                jkullick
                / raspberry-pi-chroot-armv7-qemu.md
            
            
              Last active
              March 24, 2024 14:36
            
              
                Chroot into Raspberry Pi ARMv7 Image with Qemu
              
          
    # install dependecies
apt-get install qemu qemu-user-static binfmt-support

# download raspbian image
wget https://downloads.raspberrypi.org/raspbian_latest

# extract raspbian image
unzip raspbian_latest
	package vendor_wgpu_example_fontstash

	import intr "base:intrinsics"

	import "core:fmt"
	import "core:math/linalg"
	import sa "core:container/small_array"

	import fs "vendor:fontstash"
	import "vendor:wgpu"
	#!/bin/bash

	# #########################################################
	#
	# WW WW AAA RRRRRR NN NN IIIII NN NN GGGG
	# WW WW AAAAA RR RR NNN NN III NNN NN GG GG
	# WW W WW AA AA RRRRRR NN N NN III NN N NN GG
	# WW WWW WW AAAAAAA RR RR NN NNN III NN NNN GG GG
	# WW WW AA AA RR RR NN NN IIIII NN NN GGGGGG
	#
	/**
	* Making promises
	*/
	let okPromise = Js.Promise.make((~resolve, ~reject as _) => [@bs] resolve("ok"));

	/* Simpler promise creation for static values */
	Js.Promise.resolve("easy");

	Js.Promise.reject(Invalid_argument("too easy"));
	/*
	* Example adds certain named Product Attribute fields to the product Edit screen ready for completion.
	* (Pre-requisite )
	* This saves the Shop Admin having to add them manually.
	*
	* Why might you want to do this instead of adding Custom fields? There's plenty of nice documentation on adding custom fields
	* for example: http://www.remicorson.com/mastering-woocommerce-products-custom-fields/
	*
	* Well a Product Attributes are a built in WooCommerce feature, using Terms which are a built in Wordpress feature.
	* - no add-ons required
	import React from 'react'
	import { observer } from 'mobx-react'

	function ArtistList({ uiState: { artistData } }) {
	const { data } = artistData;
	if ( !data \|\| !data.artists \|\| !data.artists.length ) {
	return <div>No artists bruh.</div>
	}
	const { artists } = data
	return (
	<!doctype html>
	<html lang="en">
	<body>
	<span id="output"></span>
	</body>
	<script>
	(function () {
	var workerBlob = new Blob(
	[workerRunner.toString().replace(/^function .+\{?\|\}$/g, '')],
	{ type:'text/javascript' }