Robert Monfera monfera

## ubo-tutorial.html
<!--
Go to Line 153 for the start of Uniform Buffer Object related code and intro

Prerequsite:

You at least know what uniforms are in the context of WebGL
and mininally understand the concepts involved in creating a square in WebGL
-->

<html>

## .block
license: gpl-3.0
redirect: https://observablehq.com/@d3/selection-join

## twitter-killjunk.js
/* NOTICE: THIS WAS MADE BACK IN 2017, OF COURSE IT'S NOT GOING TO WORK WELL NOW THAT TWITTER'S FUCKED THINGS UP */
@namespace url(http://www.w3.org/1999/xhtml);

@-moz-document domain("twitter.com") {
  [data-component-context="suggest_recap"],
  [data-component-context="suggest_who_to_follow"],
  [data-component-context="suggest_activity"],
  [data-component-context="suggest_activity_tweet"],
  [data-component-context="suggest_recycled_tweet_inline"],
  [data-component-context="suggest_recycled_tweet"]{

## bytecode.md

      
              1 file
            
          
              0 forks
            
          
              10 comments
            
          
              24 stars
            
          
                addyosmani
                / bytecode.md
            
            
              Last active
              May 28, 2022 22:40
            
              
                Thoughts on precompiling JS bytecode for delivery through a server/CDN
              
          
    Some quick thoughts on https://twitter.com/dan_abramov/status/884892244817346560. It's not ignorant at all to ask how browser vendors approach performance. On the V8 side we've discussed bytecode precompilation challenges a few times this year. Here's my recollection of where we stand on the idea:
JavaScript engines like V8 have to work on multiple architectures. Every version of V8 is different.
The architectures we target are different. A precompiled bytecode solution would require a system (e.g the server
or a CDN) to generate bytecode builds for every target architecture, every version of V8 supported and
every version of the JavaScript libraries or bundles bytecode is being generated for. This is because we would
need to make sure every user accessing a page using that bytecode can still get the final JS successfully executed.
Consider that if a cross-browser solution to this problem was desired, the above would need to be applied to JavaScriptCore,
SpiderMonkey and Chakra as well. It would need to ca

  
## FP_Observables.js
// Observable is an Union Type, with the following variants
const Empty   = () => ['EMPTY']
const Cons    = (head, tail) => ['CONS', head, tail]
const Future  = promise => ['FUTURE', promise]

// race between 2 promises; each promise will resolve to a lazy value
const lazyRace = (p1, p2) => Promise.race([p1,p2]).then(lazy => lazy())

// function composition
const compose = (...fns) => (arg) => fns.reduceRight((res, f) => f(res), arg)

## toEs6
function toEs6(script) {
  return script.replace(/var/g, 'let');
}

## state-monad.js
var push = function (value) {
  return function (stack) {
    var newStack = [value].concat(stack);
    return { value:undefined, stack:newStack };
  };
};

var pop = function () {
  return function (stack) {
    var value = stack[0];
	<!--
	Go to Line 153 for the start of Uniform Buffer Object related code and intro

	Prerequsite:

	You at least know what uniforms are in the context of WebGL
	and mininally understand the concepts involved in creating a square in WebGL
	-->

	<html>
	license: gpl-3.0
	redirect: https://observablehq.com/@d3/selection-join
	/* NOTICE: THIS WAS MADE BACK IN 2017, OF COURSE IT'S NOT GOING TO WORK WELL NOW THAT TWITTER'S FUCKED THINGS UP */
	@namespace url(http://www.w3.org/1999/xhtml);

	@-moz-document domain("twitter.com") {
	[data-component-context="suggest_recap"],
	[data-component-context="suggest_who_to_follow"],
	[data-component-context="suggest_activity"],
	[data-component-context="suggest_activity_tweet"],
	[data-component-context="suggest_recycled_tweet_inline"],
	[data-component-context="suggest_recycled_tweet"]{
	// Observable is an Union Type, with the following variants
	const Empty = () => ['EMPTY']
	const Cons = (head, tail) => ['CONS', head, tail]
	const Future = promise => ['FUTURE', promise]

	// race between 2 promises; each promise will resolve to a lazy value
	const lazyRace = (p1, p2) => Promise.race([p1,p2]).then(lazy => lazy())

	// function composition
	const compose = (...fns) => (arg) => fns.reduceRight((res, f) => f(res), arg)
	function toEs6(script) {
	return script.replace(/var/g, 'let');
	}
	var push = function (value) {
	return function (stack) {
	var newStack = [value].concat(stack);
	return { value:undefined, stack:newStack };
	};
	};

	var pop = function () {
	return function (stack) {
	var value = stack[0];