benchmark.js: measure wasm speed

benchmark - npm

//benchmarkjs.com

Getting Started With WebAssembly in Node.js | www.thecodebarbarian.com

javascript - Wasm: Uncaught (in promise) TypeError: Import #0 module="env" error: module is not an object or function Promise.then (async) (anonymous) @ (index):9 - Stack Overflow

WebAssembly.instantiate() - JavaScript | MDN

AssemblyScript Book

Quick Start | The AssemblyScript Book


AssemblyScript

Designed for WebAssembly

AssemblyScript targets WebAssembly's feature set specifically, giving developers low-level control over their code.

Familiar TypeScript syntax

Being a variant of TypeScript makes it easy to compile to WebAssembly without learning a new language.

Getting started with AssemblyScript | WebAssembly | Tutorial - YouTube

podcast: ACM ByteCast

 ByteCast Archive

11 January 2022 : Ep23 David Heinemeier Hansson

27 May 2021 : Ep16 Leslie Lamport

4 January 2021 : Ep9 Vint Cerf

2 June 2020 : Ep2 Donald Knuth

29 April 2020 : Ep1 John Hennessy & David Patterson

How to write a compiler using LLVM

 A tutorial on how to write a compiler using LLVM - Strumenta

Code Generation with Roslyn: a Skeleton Class from UML - Strumenta

Parsing SQL - Strumenta

Language2Language Transformers: machine learning to build transpilers. -

JupyterBooks with MarkDown, Sphinx, MyST

Episode #354 Sphinx, MyST, and Python Docs in 2022 - [Talk Python To Me Podcast]

Gallery of Jupyter Books — Team Documentation

Paul's free Sphinx and Markdown course: training.talkpython.fm

Sphinx: sphinx-doc.org
Python documentation: docs.python.org
ExecutableBooks: executablebooks.org
Jupyter Book: jupyterbook.org
MyST parser: myst-parser.readthedocs.io
Sphinx Book Theme: sphinx-book-theme.readthedocs.io
PyData Sphinx Theme: pydata-sphinx-theme.readthedocs.io
Sphinx Themes Gallery: sphinx-themes.org
Furo Theme: pradyunsg.me
sphinx-theme-builder: github.com
Python Documentation WG issue tracker: github.com
ReadTheDocs CZI: blog.readthedocs.com
Pandoc: pandoc.org
Google circa 1996: web.archive.org
Python doc example: docs.python.org
Tailwind doc example: tailwindcss.com/docs
Typora app: typora.io
CommonMark: commonmark.org
Watch this episode on YouTube: youtube.com
Episode transcripts: talkpython.fm

AWS Lambda + Docker + Postgres tools

 AWS Lambda PostgreSQL Client. For a while now the teams i’m working… | by Matt Houghton | Medium

Backup a database using AWS Lambda container

Using Docker on Lambda for Postgres to S3 Backups - DEV Community

book: 24 days from node.js to Rust

vinodotdev/node-to-rust

PDF: From JavaScript to Rust: A Book — A book that attempts to map common JavaScript workflows to the Rust ecosystem, if you’ve been keen to pick up the increasingly popular systems language. There’s also a GitHub repo with the source for the book.

JARROD OVERSON

JavaScript Weekly Issue 578: February 25, 2022

24 days from node.js to Rust

Temporal.io: Workflows-as-Code

Episode #124: Self-Provisioning Runtimes with Shawn "swyx" Wang - Serverless Chats Podcast

Shawn “Swyx” Wang is currently Head of DX at Temporal.io, based out of Seattle. He is also a frequent writer and speaker best known for the Learn in Public movement and recently published The Coding Career Handbook with more advice for engineers going from Junior to Senior.
Twitter: @swyx
LinkedIn: https://www.linkedin.com/in/shawnswyxwang/
Website: https://www.swyx.io/
Github: https://github.com/sw-yx
YouTube: https://www.youtube.com/swyxTV
The Swyx Mixtape: https://swyx.transistor.fm/
The Self-Provision Runtime: https://www.swyx.io/self-provisioning-runtime

Temporal - the iPhone of System Design

3 core opinions: Orchestration, Event Sourcing, and Workflows-as-Code.

The prototypical workflow state machine is a JSON or YAML file listing a sequence of steps. But this abuses configuration formats for expressing code. it doesn’t take long before you start adding features like conditional branching, loops, and variables, until you have an underspecified Turing complete “domain specific language” hiding out in your JSON/YAML schema.

[
  {
    "first_step": {
      "call": "http.get",
      "args": {
        "url": "https://www.example.com/callA"
      },
      "result": "first_result"
    }
  },
  {
    "where_to_jump": {
      "switch": [
        {
          "condition": "${first_result.body.SomeField < 10}",
          "next": "small"
        },
        {
          "condition": "${first_result.body.SomeField < 100}",
          "next": "medium"
        }
      ],
      "next": "large"
    }
  },
  {
    "small": {
      "call": "http.get",
      "args": {
        "url": "https://www.example.com/SmallFunc"
      },
      "next": "end"
    }
  },
  {
    "medium": {
      "call": "http.get",
      "args": {
        "url": "https://www.example.com/MediumFunc"
      },
      "next": "end"
    }
  },
  {
    "large": {
      "call": "http.get",
      "args": {
        "url": "https://www.example.com/LargeFunc"
      },
      "next": "end"
    }
  }
]

This example happens to be from Google, but you can compare similar config-driven syntaxes from Argo, Amazon, and Airflow. The bottom line is you ultimately find yourself hand-writing the Abstract Syntax Tree of something you can read much better in code anyway:

async function dataPipeline() {
	const { body: SomeField } = await httpGet("https://www.example.com/callA")
	if (SomeField < 10) {
		await httpGet("https://www.example.com/SmallFunc")
	} else if (SomeField < 100) {
		await httpGet("https://www.example.com/MediumFunc")
	} else {
		await httpGet("https://www.example.com/BigFunc")
	}
}