nichoth nichoth

What's the big deal with Node.js and `await`?

So I really don't like most new things. The only reason I even got involved with Node.js early on was because of its sweeping promise: "One language, spoken by developers across the world." By consolidating parallel efforts, it would accelerate the pace of innovation, and quickly lead to more transformative and disruptive developer tools. It would create tremendous value for software businesses by unlocking efficiencies in the hiring and implementation process. And best of all everyone would waste less time on boring stuff.

Still, there was a problem. While it's true most developers have touched some JavaScript callbacks up there in browserland, in the bowels of the application server, there tends to be a lot more asynchronous things going on. And that causes all sorts of issues. All those callbacks also make for a way steeper

Epidemic Broadcast Trees (explain i like i'm 5)

I want to broadcast a message to my friends around the world and I have a couple of requirements

make sure everyone definitely gets it
make sure everyone gets it soon
send as few messages as possible
it should work for everyone

How might I approach this?

low level primitives (in ascending abstraction)

hypercore works with individual posts in an append-only feed
hyperdrive abstracted filestore / works with files
hyperdiscovery create p2p swarms for hypercores, hyperdrives, and hyperdbs
hyperdb key-value database

higher level abstractions

webdb database; basically a document(?) store
dat-node built ontop of hypercore & hyperdrive, abstracts a bunch of stuff; less complex but also less flexible

Can we create a smart contract VM on nodejs using Dat?

Ethereum is a trustless network of VMs which run smart contracts submitted by users. It uses proof-of-work to synchronize state across the network, and has every node execute the contracts in order to verify the state's validity. Each transaction is stored in the blockchain for replayability. Read more about it here.

Ethereum's "trustless network" model has some disadvantages:

Transaction processing is slow - it maxes at roughly 25tx/s right now for all contracts combined.
Every transaction costs money to execute.
The entire blockchain state must be shared across the computing network.
No private transactions.

	<!DOCTYPE html>
	<html>
	<head>
	<title>Service-worker demo</title>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">


	<script>
	if ( "serviceWorker" in navigator ) {

	var nest = require('depnest')
	var MutantPullReduce = require('mutant-pull-reduce')

	exports.needs = nest({
	'sbot.pull.stream': 'first'
	})

	exports.gives = nest('bookmarks.obs.all', true)

	exports.create = function (api) {

	/**
	* Example to refresh tokens using https://github.com/auth0/node-jsonwebtoken
	* It was requested to be introduced at as part of the jsonwebtoken library,
	* since we feel it does not add too much value but it will add code to mantain
	* we won't include it.
	*
	* I create this gist just to help those who want to auto-refresh JWTs.
	*/

	const jwt = require('jsonwebtoken');

	var hypercore = require('hypercore')
	var ram = require('random-access-memory')

	var feed = hypercore(ram)

	feed.append('hello world')

	const Task = require('data.task')

	Task.prototype.alt = function (that) {
	return new Task((rej, res) =>
	this.fork(_ => that.fork(rej, res), res))
	}

	const hosts = [
	[ 'db1.mysite.com', 'user', 'password' ],
	[ 'db2.mysite.com', 'user', 'password' ],