kiprasmel

#!/usr/bin/env bash

fn() {
	base="$1"
	shift
	printf "$base with \$*\n"
	for i in  $* ; do printf "  $i\n"; done;
	printf "$base with \$@\n"
	for i in  $@ ; do printf "  $i\n"; done;
	printf "$base with \"\$*\"\n"

kiprasmel

/**
 * https://gist.github.com/kiprasmel/3fb1578e1f428dd1dd8e88683ca8c400
 *
 * put in a javascript code block under a block containing {{[[roam/js]]}} text, like so:
 * - {{[[roam/js]]}}
 *   - this code
*/

// https://roamresearch.com/#/app/developer-documentation/page/JTLUegLiI
window.roamAlphaAPI.ui

gaearon

Next.js client-only SPA example

Made this example to show how to use Next.js router for a 100% SPA (no JS server) app.

You use Next.js router like normally, but don't define getStaticProps and such. Instead you do client-only fetching with swr, react-query, or similar methods.

You can generate HTML fallback for the page if there's something meaningful to show before you "know" the params. (Remember, HTML is static, so it can't respond to dynamic query. But it can be different per route.)

Don't like Next? Here's how to do the same in Gatsby.

kiprasmel

#!/bin/sh

for p in *projects/; do
	printf "\n$p\n\n"
	for dir in $(find "./$p" -type d -maxdepth 1); do
		gitdir="$dir/.git"
		test -d "$gitdir" && {
			printf "$dir\n"
			git --work-tree="$dir" --git-dir="$gitdir" status -s
		}

kiprasmel

<!-- 
  - https://preactjs.com/guide/v10/getting-started#no-build-tools-route
    - https://preactjs.com/guide/v10/getting-started#alternatives-to-jsx
 -->
<script type="module">
  import * as preact from 'https://unpkg.com/preact?module';
  import htm from 'https://unpkg.com/htm?module';

  const h = htm.bind(preact.h);

kiprasmel

/**
 * https://gist.github.com/kiprasmel/75de24e48c8c442e55d4771768d7ba49
 */

export type Cb = () => void;

export class EventEmitter<Event extends string> {
	listeners: Map<Event, Cb[]> = new Map();

	/**

tabatkins

We've been deadlocked for a while on the pipeline operator proposal, for a few reasons. Partially it's just low implementor interest, as this is fundamentally just syntactic sugar, but also because there are three competing proposals and the proponents of each haven't been convinced by the others yet.

In this essay I hope to briefly outline the problem space, summarize the three proposals, and talk about what's gained/lost by each of them. (Spoiler: they're all nearly identical; we're arguing over very small potatoes.)

kiprasmel

#include <bits/stdc++.h>
using namespace std;

int main() {
	// replace this with `cin` or `ifstream` or whatever)
	stringstream ss("ayyy lmao asd_qwe: 69, 420,1337, nice yo\nhehe xd: 1, 2, 3, kekw pog");

	string a, b, c;
	getline(ss, a, ' '); // ayyy    (till space)
	getline(ss, b, ' '); // lmao    (till space)

kiprasmel

#!/usr/bin/env sh
# iptables_reset.sh

# get via e.g. curl ifconfig.me
MY_LOCAL_IP=""

[ -z "$MY_LOCAL_IP" ] && {
	printf "
usage:
add your local ip inside to the script, then

kiprasmel

#!/usr/bin/env bash

USER="kipras"
NAME="turbo-schedule"
TAG="$1"

[ -z "$TAG" ] && TAG="latest"

docker stop "$NAME"
docker rename "$NAME" "$NAME".old