majkinetor

script:pre-request {
  const { login } = require('./utils')

  await login(req)
}

reduz

During the past days, this great article by Sam Pruden has been making the rounds around the gamedev community. While the article provides an in-depth analysis, its a bit easy to miss the point and exert the wrong conclusions from it. As such, and in many cases, users unfamiliar with Godot internals have used it points such as following:

• Godot C# support is inefficient
• Godot API and binding system is designed around GDScript
• Godot is not production ready

In this brief article, I will shed a bit more light about how the Godot binding system works and some detail on the Godot

adrianbrad

# .golangci.yml
run:
  modules-download-mode: vendor

  skip-dirs: [vendor]

linters-settings:
  staticcheck:
    # Select the Go version to target. The default is '1.13'.
    go: "1.19"

llimllib

build:
	./node_modules/.bin/esbuild index.js --bundle --outfile=out.js

bokwoon95

-- how to model threaded comments (e.g. reddit comments) in SQL with a simple 'ancestors' column

-- The comment tree:
--          [1]
--         /    \
--       [2]    [4]
--      /   \      \
--    [3]   [7]    [6]
--   /
-- [5]

xhit

package main

import (
	"errors"
	"fmt"
	"time"
)

func main() {
	dur, _ := ParseDuration("1.000000001s")

manigandham

Various search databases and backends as alternatives to Elasticsearch.

Rust

• Sonic - github.com/valeriansaliou/sonic - lightweight & schema-less search backend
• Tantivy - github.com/quickwit-oss/tantivy - full-text search engine library inspired by Apache Lucene
• Toshi - github.com/toshi-search/Toshi - search engine built on top of Tantivy
• Bayard - github.com/mosuka/bayard - search engine built on top of Tantivy
• Meilisearch - github.com/meilisearch/meilisearch - fast and full-featured search engine

joncalhoun

gotest() {
  go test $* | sed ''/PASS/s//$(printf "\033[32mPASS\033[0m")/'' | sed ''/FAIL/s//$(printf "\033[31mFAIL\033[0m")/'' | sed ''/FAIL/s//$(printf "\033[31mFAIL\033[0m")/'' | GREP_COLOR="01;33" egrep --color=always '\s*[a-zA-Z0-9\-_.]+[:][0-9]+[:]|^'
}

Kerollmops

Core Coding Standard

Coding practices are a source of a lot of arguments among programmers. Coding standards, to some degree, help us to put certain questions to bed and resolve stylistic debates. No coding standard makes everyone happy. (And even their existence is sure to make some unhappy.) What follows are the standards we put together on the Core team, which have become the general coding standard for all programming teams on new code development. We’ve tried to balance the need for creating a common, recognizable and readable code base with not unduly burdening the programmer with minor code formatting concerns.

Table Of Contents

• Why we need Coding Standards
• Context is Important
• Stylistic Standards

• Namespaces

djg

Papers I like Pt. 1 Papers I like Pt. 2

Let's start meta:

1. Lamport - State the Problem Before Describing the Solution (1978). … 1-page memo. Read it.
2. Herlihy - Wait-free synchronization (1991) … Truly seminal. Lucid + enough good ideas for 4 papers easily.
3. Cook - How complex systems fail (1998) … 4 pages that anyone working on/with complex systems should read.