Matthew Simo matthewsimo

https://twitter.com/snookca/status/1073299331262889984?s=21

‪“‬In what way is JS any more maintainable than CSS? How does writing CSS in JS make it any more maintainable?”

‪Happy to chat about this. There’s an obvious disclaimer that there’s a cost to css-in-js solutions, but that cost is paid specifically for the benefits it brings; as such it’s useful for some usecases, and not meant as a replacement for all workflows. ‬

‪(These conversations always get heated on twitter, so please believe that I’m here to converse, not to convince. In return, I promise to listen to you too and change my opinions; I’ve had mad respect for you for years and would consider your feedback a gift. Also, some of the stuff I’m writing might seem obvious to you; I’m not trying to tell you if all people of some of the details, but it might be useful to someone else who bumps into this who doesn’t have context)‬

So the big deal about css-in-js (cij) is selectors.

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

Go to the remote repo and delete outdated branches
Then either:
- Locally cleanup only merged branches: git branch --merged | grep -v "\*" | xargs -n 1 git branch -d

Locally remove fetched, outdated branches: git for-each-ref --format='%(refname:short) %(upstream)' refs/heads/ | awk '$2 !~/^refs\/remotes/' | xargs git branch -D”

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

~~Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.~~

Build Server

Go to Digital Ocean
Create new droplet
London
Ubuntu
No apps
Add SSH keys

	// Paste this into the console

	var colors = [...document.querySelectorAll("*")].flatMap((el) => {
	const style = getComputedStyle(el);
	return [
	style.getPropertyValue("color"),
	style.getPropertyValue("background-color"),
	];
	});

	int[][] result;
	float t, c;

	float ease(float p) {
	return 3pp - 2pp*p;
	}

	float ease(float p, float g) {
	if (p < 0.5)
	return 0.5 * pow(2*p, g);

	ofPolyline temp;
	float ff = ofGetElapsedTimef();
	for (int i = 0; i < 100; i++){
	float angle = ofMap(i, 0, 100, 0, TWO_PI);
	ofPoint pt= ofPoint(400,400);
	float radius = 200 + ofSignedNoise(ff0.1, cos(angle)0.3, sin(angle)0.3) 100;
	pt += radius * ofPoint(cos(angle), sin(angle));
	temp.addVertex(pt);
	}
	temp.setClosed(true);

	Shader "ARCore/DiffuseColorWithLightEstimation"
	{
	Properties
	{
	_Color("Color", Color) = (1,1,1,1)
	_MainTex ("Base (RGB)", 2D) = "white" {}
	}

	SubShader
	{