joakim

How It Works on Mac

By default, scroll bars do not appear on Mac except when the user is scrolling and when there is hidden content. You can double check this by going to System Preferences -> General -> Show scroll bars: Automatically based on mouse or trackpad.

When you do scroll, the width of viewport and the available width of the inner content does not change from what it was. If the width was 300 pixels, it still is 300 pixels.

If you change the "Show scroll bars" setting to "Always" then the scrollbar takes up a decided amount of width - 16 pixels to be precise.[^1] Let's say your browser height is 300 pixels and your broswer width is also 300 pixels. With this setting, if you toggle the height of the body from 300 to 600, causing scrollableness, then a scrollbar will appear only have you have done the toggle. The width of your body will have gone from 300 to 284 pixels, because the scrollbar takes up space in a way that it did not in the other setting. Interestingly, if you're talking about

Cryptographic Best Practices

Putting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.

The following advice comes from years of research from leading security researchers, developers, and cryptographers. This Gist was [forked from Thomas Ptacek's Gist][1] to be more readable. Additions have been added from

NavigationExperimental notes

Containers

RootNavigationContainer

You pass the reducer to this, it actually ultimately receives all navigation calls via onNavigate, which is mostly equivalent to Redux dispatch. It setState and persisting state. it is like the redux "store"

	/*
	Funcords is a feature that combine functions and records.

	If you think about it, record is actually a dependently typed function,
	where the output type depends on the input type.

	For example,

	r = {'x': 1, 'y': 'yo'}

	const sass = require('node-sass');

	// related: https://github.com/UnwrittenFun/svelte-vscode/issues/1

	module.exports = {
	preprocess: {
	style: async ({ content, attributes }) => {
	if (!['text/sass', 'text/scss'].some(attributes.type) && !['sass', 'scss'].some(attributes.lang)) return;

	return new Promise((resolve, reject) => {

	// Trie.js - super simple JS implementation
	// https://en.wikipedia.org/wiki/Trie

	// -----------------------------------------

	// we start with the TrieNode
	function TrieNode(key) {
	// the "key" value will be the character in sequence
	this.key = key;

	// Turns out this was not too difficult.
	// By using the event loop as a global mail box ordering is even guaranteed for messages between only two actors.
	// TODO would like to try and put one actor in a web worker to get some real parallism
	// TODO would like to handle errors and have the concept of a deceased actor while a reference to an actor still exists. Probably involves creating an actor system like in Scala. Eurgh.

	var actor = {
	send: function(message) {
	var self = this;
	console.log("sending to:", self);
	setTimeout(function(){

	/**
	* Sample React Native App
	* https://github.com/facebook/react-native
	*/

	import React, { Component } from 'react';
	import {
	AppRegistry,
	StyleSheet,
	Text,

	// This is free and unencumbered software released into the public domain.

	// Marshals a string to an Uint8Array.
	function encodeUTF8(s) {
	var i = 0, bytes = new Uint8Array(s.length * 4);
	for (var ci = 0; ci != s.length; ci++) {
	var c = s.charCodeAt(ci);
	if (c < 128) {
	bytes[i++] = c;
	continue;

	/**
	* @providesModule IncrementalListView
	*/
	'use strict';

	var InteractionManager = require('InteractionManager');
	var LayoutAnimation = require('LayoutAnimation');
	var ListViewDataSource = require('ListViewDataSource');
	var RCTScrollViewManager = require('NativeModules').ScrollViewManager;
	var React = require('React');