Benjamin Devine bnjm

Created by Christopher Manning

Gallery

[![Star]

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

Projects for WebARonARKit and WebARonARCore

New Projects

Leave a comment to add a project you've created or found!

Browsers

optimize GLTF file

This optimizes a GLTF file that was exported by blender (or similar) by de-duplicating buffer views (i.e. chunks of bytes) that are equal and removing redundant accessors.

For example, 100 cubes of different scales/materials/rotations/etc should all end up using a single BufferGeometry in ThreeJS, which isn't the case with current GLTF exporters in Blender and parsers for ThreeJS.

In scenes with a lot of instancing, it can dramatically reduce total file size as well as render performance. In one test scene:

Before: 4.8MB file size, 832 THREE.Geometry instances across 832 THREE.Mesh objects
After: 661KB file size, 13 THREE.Geometry instances across 832 THREE.Mesh objects

I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.

I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.

"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr

	// # Mocha Guide to Testing
	// Objective is to explain describe(), it(), and before()/etc hooks

	// 1. `describe()` is merely for grouping, which you can nest as deep
	// 2. `it()` is a test case
	// 3. `before()`, `beforeEach()`, `after()`, `afterEach()` are hooks to run
	// before/after first/each it() or describe().
	//
	// Which means, `before()` is run before first it()/describe()

	let spriteKitScene = SKScene(size: CGSize(width: 1276.0 / 2.0, height: 712.0 / 2.0))
	var videoSpriteKitNode:SKVideoNode?
	let videoNode = SCNNode()

	videoNode.geometry = SCNPlane(width: videoNodeWidth, height: videoNodeHeight)

	// using SpriteKit scene with videonode inside
	//
	spriteKitScene.scaleMode = .AspectFit

	/* Fuzzy Search in JavaScript in 66 bytes by SpeedyNinja
	Creates a Regex of the Form x.y.z.* for query xyz and tests it against the list of terms
	*/
	f=t=>s=>t.filter(x=>eval("/"+s.replace(/./,"$&.*")+"/gi").test(x))

	/*
	Usage:
	var search = f(["list", "of", "search", "terms"])
	search("er") -> ["search", "terms"]
	^ ^ ^^