repi

What to evaluate and consider before adding usage of new third-party crates.

These are not exact requirements but questions to investigate and discuss to help reason around the health, safety, maintainability, and more around crates.

This can also be read as an opinionated guide for crate authors of what our (Embark's) guidelines and recommendations are, though should not be taken too literally.

Legend: 🔒 Must have, ⭐️ Should have, 👍 Nice to have, ℹ️ Info

DanB91

THIS GIST IS OUT OF DATE!  Please use my new project template here to get started with Zig on Playdate:
https://github.com/DanB91/Zig-Playdate-Template


The rest of this is preservied for historical reasons:


This is a small snippet of some code to get you started for developing for the Playdate on Zig.  This code should be used as a starting point and may not compile without some massaging.  This code has only been tested out on macOS and you'll need to modify the addSharedLibrary() portion of build.zig to output a .dll or .so instead of a .dylib, depending on you platform.

This code will help you produce both an executable for the Playdate simulator and also an executable that actually run on the Playdate hardware.  

berkus

1. Separation of immutable and mutable logic

Quite a lot of different people have been on the same trail of thought. Gary Bernhardt's formulation of a "functional core, imperative shell" seems to be the most voiced.

"Boundaries" - Gary Bernhardt

"Imperative shell" that wraps and uses your "functional core".. The result of this is that the shell has fewer paths, but more dependencies. The core contains no dependencies, but encapsulates the different logic paths. So we’re encapsulating dependencies on one side, and business logic on the other side. Or put another way, the way to figure out the separation is by doing as much as you can without mutation, and then encapsulating the mutation separately. Functional core — Many fast unit tests. Imperative shell — Few integration tests

https://www.youtube.com/watch?v=yTkzNHF6rMs

RadicalZephyr

// Download all the custom emoji your slack team have created!

// Start by going to the "Customize Emoji" screen for your Slack team.
// Open up a browser console and run the following JS

var pattern = new RegExp("https://emoji.slack-edge.com/.*?/([^/]+?)/[^/]+(\.png|jpg|gif)");

function link_text (url) {
  var match = pattern.exec(url);
  if (match) {

bethanylong

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

const int BUFSIZE = 1024;
const int ARBITRARY_THRESHOLD = 3;

int is_uppercase(char ch) {
    return ch >= 'A' && ch <= 'Z';
}

garybernhardt

This document has moved!

It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.

sampollard

#!/bin/bash
for song in $(find ~ -iname *.mp3)
do
	title=$(id3info $song | awk -F ':' '/TIT2/{print $NF}')
	id3tag -s "$title (feat. Minions)" $song
done

bethanylong

#include <stdlib.h>
#include <unistd.h>
#include <stdio.h>
#include <string.h>

#include <sys/socket.h>
#include <netpacket/packet.h>
#include <net/ethernet.h>

#include <netdb.h>

lelandbatey

Description

This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.

The script is here:

#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"

Results

bgschiller

all: thread_prng adversary Makefile advantages

thread_prng: thread_prng.c
	gcc --std=c99 -o thread_prng -lpthread thread_prng.c

adversary: adversary.c
	gcc --std=c99 -o adversary adversary.c

advantages: adversary thread_prng
	for option in r m; do \