Berkus Decker berkus

The introduction to Reactive Programming you've been missing

So you're curious in learning this new thing called (Functional) Reactive Programming (FRP).

Learning it is hard, even harder by the lack of good material. When I started, I tried looking for tutorials. I found only a handful of practical guides, but they just scratched the surface and never tackled the challenge of building the whole architecture around it. Library documentations often don't help when you're trying to understand some function. I mean, honestly, look at this:

Rx.Observable.prototype.flatMapLatest(selector, [thisArg])

Projects each element of an observable sequence into a new sequence of observable sequences by incorporating the element's index and then transforms an observable sequence of observable sequences into an observable sequence producing values only from the most recent observable sequence.

Real World Specification

(aka "Algebraic JavaScript Specification")

This project specifies the behavior of a number of methods that may optionally be added to any object. The motivation behind this is to encourage greater code reuse. You can create functions that just rely on objects having implementations of the methods below, and in doing so you can make them work with a wide variety of different, but related data structures.

Definitions

For the purposes of this, spec, an "entity" is an object that has an [[equivalent]] operation (see bellow) and may implement some or all of the other methods.

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

WASM Rust to Node Example

Use only > 8.x.x NodeJS version

Install Rust before using this tutorial: curl https://sh.rustup.rs -sSf | sh

Create dirs:

mkdir wasmRustNodeExample

cd wasmRustNodeExample

Physical layer

The dongle itself is sending out data using 802.11a (5 GHz WiFi) with OFDM and 6 Mbit/s data rate:

Radiotap Header v0, Length 38
    Header revision: 0
    Header pad: 0
    Header length: 38
    Present flags

	#===============================================================================
	# Filename: boost.sh
	# Author: Pete Goodliffe
	# Copyright: (c) Copyright 2009 Pete Goodliffe
	# Licence: Please feel free to use this, with attribution
	# Modified version
	#===============================================================================
	#
	# Builds a Boost framework for the iPhone.
	# Creates a set of universal libraries that can be used on an iPhone and in the

	#include <stdio.h>
	#include <stdlib.h>
	#include <stdint.h>
	#ifdef _MSC_VER
	#include <intrin.h> /* for rdtscp and clflush */
	#pragma optimize("gt",on)
	#else
	#include <x86intrin.h> /* for rdtscp and clflush */
	#endif

	class utf8_text_view {

	const char *text;
	size_t bytes_count;
	public:
	friend class iterator;
	class iterator {
	const utf8_text_view &parent;
	size_t offset;
	public:

	#![feature(result_map_or_else)]

	extern crate serde; // 1.0.84
	extern crate serde_derive; // 1.0.84
	extern crate serde_json; // 1.0.34

	use serde::Serialize;

	#[derive(Debug, Serialize)]
	#[serde(tag = "status", content = "result")]

	trait Trait: AsTrait {
	fn get_answer(&self) -> i32;
	}

	struct S;

	impl Trait for S {
	fn get_answer(&self) -> i32 { 42 }
	}