ebidel

Moved to https://github.com/ebidel/puppeteer-examples/blob/master/monitor_internet_connection.js

ebidel

/**
 * @author ebidel@ (Eric Bidelman)
 * License Apache-2.0
 */
 
// Prints the bytes cached by service worker. Breaks out each cache
// overall in-memory bytes used by the Cache Storage API for the site.
 
async function getCacheStoragesAssetTotalSize() {
  // Note: opaque (i.e. cross-domain, without CORS) responses in the cache will return a size of 0.

steveklabnik

#![feature(lang_items)]
#![no_std]

#[no_mangle]
pub fn add_one(x: i32) -> i32 {
    x + 1
}


// needed for no_std

slightlyoff

Background

One of the biggest missed opportunities thus far with HTTP/2 ("H/2") is that we are not yet able to sunset WebSockets in favor of H/2. Web Sockets and H/2 both support multiplexing messages bi-directionally and can send both textual and binary data.

Server Sent Events ("SSE"), by contrast, are not bi-directional (they're a "server-push-only" channel) and binary data cannot be sent easily. They are, however, very simple to implement. Adding to the menagerie of options, RTCPeerConnection can also be used to signal data to applications in a low-latency (but potentially lossy) way.

Because H/2 [does not support the handshake (upgrade) that WebSockets use to negotiate a connection](https://daniel.haxx.se/blog/2016/06/15/no-websockets-

mortenson

// Put this file in a directory where @stencil/core exists in node_modules, then run:		+var stencil = require('@stencil/core/server');
// $ echo $HTML | node ssr.js [root] [build-dir] [namespace]		
// Full example from my use case:		
// $ echo '<sam-text text="Hello, world"></sam-text>' | node ssr.js /var/www/stencil/sams-components/ ../dist sam		
// Pipes are used because HTML strings can be really long, and bash has limits on how large argument lists can get (~256k usually).		
var stencil = require('@stencil/core/server');
var args = process.argv.slice(2);
if (args.length < 3) {
  console.error('Not enough args');
}

developit

state-machine-component

A tiny (265 byte) utility to create state machine components using two pure functions.

🔥 JSFiddle Demo

Usage

The API is a single function that accepts 2 pure functions as arguments:

simevidas

// only polyfill .finished in browsers that already support animate()
if (document.body.animate) {
  
  // Chrome does not seem to expose the Animation constructor globally
  if (typeof Animation === 'undefined') {
    window.Animation = document.body.animate({}).constructor;
  }

  if (Animation.prototype.finished === undefined) {
    Object.defineProperty(Animation.prototype, 'finished', {

brson

Edit: This list is now maintained in the rust-anthology repo.

• Introduction
  • Understanding Over Guesswork
  • An Alternative Introduction to Rust
  • Rust and CSV Parsing
• Ownership
  • Where Rust Really Shines
  • Rust Means Never Having to Close a Socket
• The Problem with Single-threaded Shared Mutability

jorgecasar

#!/usr/bin/env node

const fs = require("fs");
const path = require("path");
const util = require('util');
const readFile = util.promisify(fs.readFile);
const writeFile = util.promisify(fs.writeFile);

function throwError(err) {
  throw err;

joshbuchea

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example