vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

armornick

#include <stdio.h>
#include <SDL2/SDL.h>
#include <SDL2/SDL_image.h>

#define WIDTH 800
#define HEIGHT 600
#define IMG_PATH "exit.png"

int main (int argc, char *argv[]) {

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

VictorTaelin

async/await is just the do-notation of the Promise monad

CertSimple just wrote a blog post arguing ES2017's async/await was the best thing to happen with JavaScript. I wholeheartedly agree.

In short, one of the (few?) good things about JavaScript used to be how well it handled asynchronous requests. This was mostly thanks to its Scheme-inherited implementation of functions and closures. That, though, was also one of its worst faults, because it led to the "callback hell", an seemingly unavoidable pattern that made highly asynchronous JS code almost unreadable. Many solutions attempted to solve that, but most failed. Promises almost did it, but failed too. Finally, async/await is here and, combined with Promises, it solves the problem for good. On this post, I'll explain why that is the case and trace a link between promises, async/await, the do-notation and monads.

First, let's illustrate the 3 styles by implementing

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

bkaradzic

Why I think Immediate Mode GUI is way to go for GameDev tools

Prerequisites

Before you continue, if you don't know what IMGUI is don't bother reading this post, just ignore it, don't write anything in comments section, etc. If you're curious about IMGUI see bottom of this post, otherwise continue whatever you were doing, this post it's not for you. Thanks!

If you know what IMGUI is, for context read following presentations and blog posts:

• Insomniac’s Web Tools Postmortem

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]

majkinetor

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

  await login(req)
}